Cable assembly

ABSTRACT

A cable assembly may include an outer jacket, a printer circuit board including light emitting diodes, and a cable configured to transmit information. The outer jacket may include a channel opening and the printed circuit board may be configured to be positioned within the channel opening and between the cable and the outer jacket. Another cable assembly may include an inner jacket, an outer jacket, a printed circuit board including light emitting diodes, and a cable configured to transmit information. The inner jacket may include a channel opening, and the printer circuit board may be configured to be positioned within the channel opening and between the inner jacket and the outer jacket.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. application Ser. No.15/246,635, filed Aug. 25, 2016, which is a continuation of U.S. patentapplication Ser. No. 14/849,746, filed Sep. 10, 2015, which is acontinuation of U.S. patent application Ser. No. 14/217,259, filed Mar.17, 2014, which claims the benefit of U.S. Provisional Application No.61/786,460 filed on Mar. 15, 2013, each of which is incorporated byreference herein in its entirety.

This application also claims the benefits of U.S. ProvisionalApplication No. 62/554,912, filed Sep. 6, 2017, entitled “System andMethod for Detecting, Locating, and/or Identifying Disturbances in anInformation Transmission Line,” which is incorporated by referenceherein in its entirety.

FIELD OF INVENTION

The present invention relates to detection of a disturbance on aninformation transmission line, including, for example, disturbancelocation identification, disturbance type identification,disturbance-triggered sensory indicators, disturbance detectionhandling, or cable assemblies with respect to a physical transmissionline.

SUMMARY

Aspects of the invention relate to a cable assembly with respect to aphysical transmission line.

In some embodiments, a cable assembly may include an outer jacket, aprinted circuit board including light emitting diodes, and a cableconfigured to transmit information. The outer jacket may include achannel opening, and the printed circuit board may be configured to bepositioned within the channel opening and between the cable and theouter jacket.

In some embodiments, a cable assembly may include an inner jacket, anouter jacket, a printed circuit board including light emitting diodes,and a cable configured to transmit information. The inner jacket mayinclude a channel opening, and the printed circuit board may beconfigured to be positioned within the channel opening and between theinner jacket and the outer jacket.

In some embodiment, an outer jacket for a cable that transmitsinformation may include an outer layer, and an inner layer, where theinner layer comprises a channel opening to allow a plurality of lightemitting diodes to be housed within the channel opening.

In some embodiments, an inner jacket for a cable that transmitinformation may include an inner layer, and an outer layer, where theouter layer comprises a channel opening to allow a plurality of lightemitting diodes to be housed within the channel opening.

These and other aspects of the present patent application, as well asthe methods of operation and functions of the related elements ofstructure and the combination of parts and economies of manufacture,will become more apparent upon consideration of the followingdescription and the appended claims with reference to the accompanyingdrawings, all of which form a part of this specification, wherein likereference numerals designate corresponding parts in the various figures.It is to be expressly understood that the drawings are for the purposeof illustration and description only and are not intended as adefinition of the limits of the present patent application. It shallalso be appreciated that the features of one embodiment disclosed hereincan be used in other embodiments disclosed herein. As used in thespecification and in the claims, the singular form of “a”, “an”, and“the” include plural referents unless the context clearly dictatesotherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system architecture, in accordance with one or moreembodiments;

FIG. 2 illustrates an infrastructure management system, in accordancewith one or more embodiments;

FIG. 3 illustrates a dashboard, in accordance with one or moreembodiments;

FIG. 4 illustrates a zone screen, in accordance with one or moreembodiments;

FIG. 5 illustrates a flowchart for monitoring alerts, in accordance withone or more embodiments;

FIG. 6 illustrates a fiber forensic graphical display, in accordancewith one or more embodiments;

FIG. 7 illustrates a flowchart for processing alerts, in accordance withone or more embodiments;

FIG. 8 illustrates a flowchart of a trunk cable processing subprocess,in accordance with one or more embodiments;

FIG. 9 illustrates a flowchart of a create alarm subprocess, inaccordance with one or more embodiments;

FIG. 10 illustrates a flowchart for a process to disable data, inaccordance with one or more embodiments;

FIG. 11 illustrates a flowchart for processing open warnings, inaccordance with one or more embodiments;

FIG. 12 illustrates a chart showing a process for case resolution, inaccordance with one or more embodiments;

FIG. 13 illustrates a case detail screen, in accordance with one or moreembodiments;

FIG. 14 illustrates a flowchart for continued monitoring during casemanagement, in accordance with one or more embodiments;

FIG. 15 illustrates a system for facilitating detection of a disturbanceon an information transmission line, in accordance with one or moreembodiments;

FIG. 16 illustrates sensor data obtained from a sensor, in accordancewith one or more embodiments;

FIG. 17 illustrates a physical transmission line and sensors placed atdifferent locations on a physical transmission line, in accordance withone or more embodiments;

FIG. 18 illustrates sensor data obtained from sensors, in accordancewith one or more embodiments;

FIG. 19 illustrates a system for identifying a location of a disturbanceevent, in accordance with one or more embodiments;

FIG. 20 illustrates a system for identifying a location of a disturbanceevent, in accordance with one or more embodiments;

FIG. 21 illustrates a user interface, in accordance with one or moreembodiments;

FIG. 22 illustrates sensor data and signature data, in accordance withone or more embodiments;

FIG. 23 illustrates a comparison between sensor data and signature data,in accordance with one or more embodiments;

FIG. 24 illustrates tables including data, in accordance with one ormore embodiments;

FIG. 25 illustrates a flowchart describing a method for identifying alocation of a disturbance event on a physical transmission line, inaccordance with one or more embodiments;

FIG. 26 illustrates a flowchart describing a method for identifying alocation of a disturbance event on a physical transmission line, inaccordance with one or more embodiments;

FIG. 27 illustrates a flowchart describing a method for identifying alocation of a disturbance event on a physical transmission line, inaccordance with one or more embodiments;

FIG. 28 illustrates a flowchart describing a method for identifying atype of a disturbance event on a physical transmission line, inaccordance with one or more embodiments;

FIGS. 29A and 29B illustrate a cable assembly, in accordance with one ormore embodiments;

FIG. 30 illustrates a circuit, in accordance with one or moreembodiments;

FIGS. 31A, 31B, 31C, and 31D illustrate a cable assembly, in accordancewith one or more embodiments;

FIGS. 32A and 32B illustrate a cable assembly, in accordance with one ormore embodiments;

FIG. 33 illustrates an architecture and operation of a visual indicationsystem; and

FIG. 34 illustrates an architecture and operation of a visual indicationsystem, in accordance with one or more embodiments.

DETAILED DESCRIPTION

All publications, patents, and patent applications cited in thisspecification are hereby incorporated by reference in their entirety.The detailed description provided below in connection with the appendeddrawings is intended as a description of exemplary embodiments and isnot intended to represent the only forms in which the invention may beconstructed or utilized. The same or equivalent functions and sequencesmay be accomplished by different embodiments as will be appreciated bythose skilled in the art.

FIG. 1 illustrates a block diagram of a system 100 according to anembodiment. System 100 may be used to provide proactive real-time alarmmonitoring of dark fiber intrusions and may distribute notification ofalarms of suspected tampering to a variety of endpoints. System 100 mayinclude a manager engine 101, a manager database server 102, a managerweb server 103, and a manager engine listener 104. In an embodiment,system 100 may include one or more components that functions as any ofthe manager engine, manager database server, manager web server, andmanager engine listener.

System 100 may integrate with a variety of network devices to offeralarm detection and alarm response capabilities in a consolidatedsystem. In an embodiment, system 100 may integrate with Passive OpticalNetwork (PON) equipment, Optical Circuit Switch equipment, Optical TestAccess Point equipment, and Network Analyzers to stop and start dataflow to network endpoints, re-route data flow, and record or furtheranalyze data when alarms are detected and resolved. Alarm events may becaptured in a case management oriented workflow for auditing andanalytics.

System 100 may provide the ability for complete network mapping ofcomponents starting from a source Optical Line Terminal (OLT) down to anend user Optical Network Terminal (ONT). Network components may beenrolled and maintained in system 100 in a logical and efficient manner.System views and reports may be leveraged to inspect an entire networkas well as each data run.

System 100 may handle the coordination of tasks between dark fiber alarmmonitoring devices and PON equipment through backend adapters leveragingSimple Network Management Protocol (SNMP) traps and Secure Shell (SSH)protocols. System 100 may be monitored actively and passively to assureevents are not missed.

System 100 may offer a secure web user interface to provide networkoperations center (NOC) oriented dashboards for proactive monitoring.Notification of events may be handled in a guaranteed delivery mannerover SMTP and HTTP to assure best effort notification to a targetedendpoint so first responders can focus on the status of the remainingsystem. Maps and images may be immediately provided with floor planlayouts overlaid with network diagrams for an alarmed area to reducecritical decision times for resolving alarms. System 100 may allow staffto identify a suspected intrusion event, isolate its location, notifyresponder groups, execute planned remediation, and track its history.

In an embodiment, system 100 offers a warning threshold technology tosuppress the occurrence of nuisance alarms. A configurable threshold mayallow system 100 to filter out accidental or environmental disturbancesfrom actual intrusion attempts.

System 100 may integrate into an existing enterprise by providingconsolidated alerts to ‘north-bound’ systems over SNMP. System 100 mayalso integrate with any existing Active Directory authentication systemto assure its operation is consistent with pre-established IT securitypolicies and site practices. System 100 may be supported by a relationaldatabase to provide redundancy, durability, recovery protection, andtools for data extraction and analysis.

In an embodiment, system 100 may provide health reports by providinganalytics and reporting on all warnings and alarms captured by system100. System 100 may provide trend reporting and predictive analysis.System 100 may publish and disseminate the results of the analysis to aconfigurable group of users at a configurable time period and frequency.

In an embodiment, system 100 may provide infrastructure management forPON Systems. System 100 may provide a graphical and textual depiction ofan end to end path for a circuit. For example, one end may start from aport on an optical line terminal and/or network switch joined with aport on an intrusion detector then continue to an optical circuit switchthen continue through a trunk cable then continue to a splitter thencontinue to a zone box then continue to a fiber run to an user area thencontinue to a user end device, such as an optical network terminal. Eachof the devices, passive or active, and each cable run may be representedin the system graphically and textually.

System 100 may provide the ability to add, modify, or deleterepresentative circuit paths. System 100 may track device types,identification numbers, and locations for each device. System 100 maydisplay each circuit path overlaid on a physical diagram, such as abuilding or floor computer-aided design (CAD) diagram. System 100 mayprovide querying and reporting capabilities for each device. System 100may highlight a circuit path when displayed in a graphical view.

Turning to FIG. 2, a schematic diagram showing an overview of aProtective Distribution System (PDS) and information technology (IT)infrastructure management system according to an embodiment is shown. Inone embodiment, system 200 may be system 100 described above. In oneembodiment, system 200 may manage an intrusion detector 202, whichmonitors a building 201. System 200 may provide the ability to receivealerts when intrusion detector 202 detects intrusion attempts. System200 may also provide the ability to manage certain features of intrusiondetector 202. As will be explained in greater detail below, suchfeatures may include learning mode, configuration, enabling anddisabling monitoring on a channel port, and reading and updating athreshold setting. Exemplary intrusion detectors that system 200 mayintegrate with are Network Integrity Systems' INTERCEPTOR, VANGUARD, andINTERCEPTOR LD2.

In one embodiment, system 200 tracks a floor 203 of building 201 that ismonitored by intrusion detector 202. Each monitored floor 203 maycontain one or more zone groups 204. Within each zone group 204 may be acollection of zones 205, each of which may correspond to a singlechannel port 206 on intrusion detector 202. Though not depicted in thefigure, system 200 may also be used to manage a collection of campuses,each of which may contain a collection of buildings.

System 200 may manage a collection of intrusion detectors 202. Intrusiondetector 202 may contain a channel port 206, which corresponds to a zone205. A zone 205 correlates to a physical location that is beingmonitored by system 200. A zone 205 may have an image 207, which mayinclude computer-aided design drawings, first person perspective images,or video, to aid users in inspections. A zone 105 may also be associatedwith a contact personnel 208. Contact personnel 208 may be notified inthe event of an intrusion attempt.

System 200 may be configured so that a zone 205 has a data port address209 associated with the zone to integrate with a data providingnetworking equipment, such as an optical circuit switch or optical lineterminal and/or network switch. In the event of an intrusion attempt inzone 205, system 200 may disable or re-route data by sending a commandto a networking equipment using data port address 209. System 200provides the ability to enable or disable data on a specific port andalso provide the ability to read and update details for a port. Someexample devices that system 200 may integrate with are Tellabs PON,Zhone PON, and Motorola POL.

Zone 205 may also have a physical security device address 210 associatedwith the zone. In the event of an intrusion attempt in zone 205, system200 may adjust physical security including locking doors, recording onIP based cameras, etc. by sending a command to physical security address210.

System 200 may also manage an optical circuit switch 211. Opticalcircuit switch 211 may provide the ability to disable, enable, orre-route an optical transmission. Optical circuit switch 211 may have anoptical line terminal and/or network switch 212. Optical line terminaland/or network switch 212 may convert and provide a fiber optical signalto a data network. System 200 may also provide the ability to perform abulk enrollment of a cross connect defined during initial installationor subsequent reconfiguration. An example device that system 200 mayintegrate with is the Calient S320 or CyberSecure Cyber Patch Panel.

Optical circuit switch 211 may have an optical test access point 213.Optical test access point 213 may allow system 200 to provide an abilityto route or copy network data. Optical test access point 213 may deliveran identical copy of network traffic to a network analytic tool, such asa network monitor 214, a security monitor 215, a network recorder 216, anetwork analyzer 217, and other analytic tools. An example of an opticaltest access point device that system 200 may integrate with is theMimetrix OpticalTAP.

Turning to FIG. 3, a dashboard 300 according to an embodiment is shown.Dashboard 300 may provide a consolidate view from a system and allownetwork personnel to determine the health of a network with multiplevisual indicators.

Intrusion detectors panel 301 may display a list of all intrusiondetectors managed by a system. Each intrusion detector displays acolored icon for a channel port. The colored icons may correlate to alabel provided in legend 307. Each intrusion detector may be associatedwith a unique label, which may include information such as a userdefined name, IP Address, etc. The background for the intrusion detectoras shown in intrusion detector panel 301 may be programmed to changeaccording to the status of the intrusion detector. For example, thebackground for an intrusion detector with a channel port in an alarmedstate may be colored red. The list of intrusion detectors may befiltered to a building specific intrusion detector when a building isselected in a building drop down list 308 or when a building icon isselected in a map view panel 302.

Map view panel 302 may be configured to display a map image with visualindicators for a building managed by a system. The location of thevisual indicators may be based on the geographic coordinates of abuilding. The color of the visual indicator may provide a combinedstatus for each of the intrusion detector's channel ports managed in abuilding. According to one embodiment, the background colors may bedetermined in the following hierarchy:

-   -   If one or more channel ports are in an alarmed state, the color        will be red.    -   If one or more channel ports are in a warning state and no        channel ports are in an alarmed state, the color will be yellow.    -   If no channel ports are in an alarmed or a warning state, the        color will be green.

Building list 308 may contain the building names for all of thebuildings managed by a system. Building list 308 may be set to a defaultoption, e.g. option ‘A1’, if there are multiple buildings managed by asystem. Otherwise, the list may default to a single building managed bya system. When a user selects a building, a system may filter a list ofintrusion detectors in intrusion detector panel 301 to only show thedevices managed in the selected building.

An incident log panel 303 may display a list of events captured orenacted by a system in response to an alert. In one embodiment, incidentlog panel 303 may display Incident Date, Room Name, Intrusion DetectorName, Zone Name, and Incident Message for an incident. An incident logmay contain the most recent incidents for a given time parameter whichmay be configured in a system.

A summary report panel 304 may display a total number of zones monitoredby a system. Also included may be the number of active alarms in asystem as well as the number of active warnings. Summary report panel304 may also include a chart of all warnings and alarms captured by asystem in a specified time period, such as the last 7 days or the last30 days.

An open incidents panel 305 may include a list of open cases. Openincidents panel 305 may list the ID, Date Opened, and Status for an opencase.

An active warnings panel 306 may include a list of all open and activewarnings. As will be described in more detail below, active warnings maybe set when a set number of disturbances or alerts are captured in adefined amount of time before reaching a configured alarm threshold. Theactive warning feature may be known as a Zonar Warning System, a VisualActive Alert Indicator. Active warnings panel 306 may also display agraphical chart to show the number of disturbances or alerts captured bya system for a given zone as well as the alarm threshold level for thegiven zone. When there are no active incidents, a system may display thelast number of warning events on the screen, such as the last 5 warningevents.

Turning to FIG. 4, a zone screen display 400 according to an embodimentis shown. Zone screen display 400 may show a live representative view ofa zone monitored by an intrusion detector. Zone screen display 400 mayshow a gauge 401, which may be known as a Zonar Warning Gauge, whichdisplays a current active warning count received by a zone and a currentpower level reading for a zone. In the event of receiving an alert, zonescreen display 400 may show the current alert count and the numericalarm threshold value by displaying the values in a gauge 401.Similarly, in the event of receiving an alert, zone screen display 400may show the severity of the alert by displaying a disturbance level ina power meter icon 402.

In one embodiment, power meter icon 402 may display the followinglevels:

-   -   Minor—based on a configurable threshold on a lower end of a        disturbance spectrum.    -   Moderate—based on a configurable threshold in between a Minor        and a Major threshold.    -   Major—based on a configurable threshold on a higher end of a        disturbance spectrum.    -   Critical—indicates a boundary alarm, which may occur when a        cable is damaged or removed from an intrusion detector port.

Zone screen display 400 may also show a media 403 related to a zone.Media 403 may be in an image, video, or document format. A system mayallow users with the appropriate privileges to add or remove a zonemedia and enter the required descriptive text for each media item. Zonescreen display 400 may include additional section 404 to displayinformation such as status of the zone, time of last alarm,alarm/warnings in the past 24 hours/7 days/30 days, and notificationlist for the zone.

Turning to FIG. 5, a flowchart for creating an alert 500 according to anembodiment is shown. In 501, an intrusion detector monitors a fiberoptic cable. In one embodiment, monitoring may be performed by comparinga light transmitted to a light received in order to detect if adisturbance has occurred. In other embodiments, monitoring may beperformed on vibration readings, frequency readings, changes in dB,optical time-domain reflectometer (OTDR), acoustic readings, distancedetermination based on reflective sensors, or combinations thereof. Whena disturbance is detected, the disturbance may be compared to a definedthreshold in 502. If the disturbance is less than the defined threshold,the intrusion detector may return to monitoring a fiber optic cable in501. If the disturbance is greater than a defined threshold, theintrusion detector may send an alert to a target based on a configuredsetting.

In one embodiment, in 503 and 504, an intrusion detector configured tosend simple network management protocol (SNMP) traps may send SNMP trapsto configured targets. In 505 and 506, an intrusion detector configuredto send Syslog entries may send Syslog entries to configured targets.

In one embodiment, a detected disturbance may be presented to a user asa graphical representation. FIG. 6 shows a screen shot of one embodimentof a graphical representation of detected disturbances. Graph 601 showsa detected disturbance as a function of time. The graphical points maybe plotted based on the level of dB difference registered on thetransmission line during the disturbance and represented accordinglywith a unique graphical icon. Additional graphical points may be plottedbased on vibration and acoustic calculations registered on thetransmission line during the disturbance and represented accordinglywith a unique graphical icon. Summary section 602 shows differentcharacteristics of the detected disturbances. The graphicalrepresentation may include time characteristics of the detecteddisturbance including the start time, end time, and total duration ofthe detected disturbance. The graphical representation may includedisturbance characteristics of the detected disturbance including themaximum optical loss measured in dB, the number of registered vibrationor acoustic events, the detection of cable damage, and the total numberof distinct disturbances. The graphical representation may be used by auser to determine whether an immediate alarm response is required andwhich alarm response team member would be able to perform the on-siteinspection. Similarly, the graphical representation may be used toindicate to the user where to perform the onsite inspection first. Thegraphical representation showing a short duration with fluctuating dBloss may indicate that inspection starts where the transmission line isreadily exposed such as in a telecommunications closet. The graphicalrepresentation showing a long duration starting with many vibration oracoustic disturbances followed by multiple fluctuating dB lossdisturbances may indicate an injection of an optical tap and that theinspection include a visual inspection of the entire transmission line.The graphical representation showing optical signatures indicative ofaccidental contact with a low severity would be represented accordingly.Similarly, optical signatures of a sever event such as the insertion ofa fiber optic tap would be represented accordingly. While the graphicalrepresentation shown in FIG. 6 and described herein depicts an exemplarygraphical representation of the detected disturbance, other graphicalrepresentations arranged with different plot points may be implementedbased on different interfaces with various intrusion detection hardware.

In FIG. 7, a flowchart for alert processing 700 by a system according toan embodiment is shown. In 701, a system may keep an open port to listenfor an alert. In 702, the system determines if an alert has beenreceived by a target. If an alert has been received, the systemtranslates the alert to determine a zone number for the alert. In 703,the system determines if the alert is a boundary alarm. Boundary alarmsmay be classified as critical severity. If the alert is a boundaryalarm, the system creates an alarm as defined in ‘create alarm’ subprocess 900.

If the system determines that the alert is not a boundary alarm in 703,the system may check in 704 to see if multiple warnings above a definedthreshold or criteria in a have been received in a defined period oftime. For example, the system may check to see if there have been 3other previous warnings occurring within the past 24 hours for the zone.If the zone does have multiple warnings that meet a defined criteria,the system creates an alarm as defined in ‘create alarm’ sub process900.

If the system determines in 704 that the zone has not have multiplewarnings that meet a defined criteria, the system may check to see ifthe zone has an active warning counter in 705. The system creates a newwarning counter for a zone in 706 if the zone does not have an activewarning counter. If the zone does have an active warning counter, thesystem opens the warning counter in 707. With an active warning counteridentified for the zone, the system increments the warning count for thezone in 708. In 709, the system determines the status of the zone. Ifthe zone is in a warning mode, the system proceeds to a trunk cableprocessing sub process 800. A warning mode may be defined as a warningcount of greater than 1. If the zone is not in a warning mode, thesystem sets the zone to a warning status in 710 and then proceeds to‘trunk cable processing’ sub process 800.

In one embodiment, the system evaluates trunk cable processing in a‘trunk cable processing’ sub process 800. After the trunk cableprocessing sub process, the system moves on to 711 to determine if thewarning count exceeds the defined threshold for the zone. If the warningcount exceeds the defined threshold for the zone, the system creates analarm in ‘create alarm’ sub process 900 and then returns to 701 tolisten for alerts. If the warning count does not exceed the definedthreshold for the zone, the system returns to 701 to listen for alerts.While the flowchart shown in FIG. 7 and described herein depicts anexemplary workflow for processing an alert, other workflows arranged ina different order may be implemented.

In FIG. 8, a flowchart for ‘trunk cable processing’ sub process 800according to an embodiment is shown. In 801, a system determines if thezone is a trunk zone. In one embodiment, a trunk zone may be defined asa zone that includes a trunk cable. A trunk cable may be co-bundled withmonitoring cables for each floor. At each floor, the cables dedicated tothat floor may distribute out to the floors. A trunk cable and remainingfloor cables may continue down a riser closet (e.g. communicationnetwork closets that traverse up and down an area of a building). Havinga dedicated trunk zone that may be monitored by a system may allow for alogical separation of user zones (e.g. network cables distributing datathroughout a floor of a building) from a riser closet and a sourcecloset (e.g. place where network data for a building originates).Without a trunk cable, on an intrusion or disturbance, an investigatormay be required to inspect an entire user zone and then back up a risercloset and back to a source closet. Logical separation may allow formeeting an inspection requirement, such as an inspection being requiredwithin 15 minute of an alert.

If the zone is a trunk zone, the system proceeds to 809 to evaluate thealert as a standard zone and returns to step 711 as described above. Ifthe zone is not a trunk zone, the system continues to 802 to determineif the trunk zone is in a warning or an alarmed status. If the system isnot in a warning or alarmed status, the system proceeds to 809 toevaluate the alert as a standard zone and returns to step 711 asdescribed above. If the trunk zone is in a warning or an alarmed status,the system proceeds to 803 and determines if a warning time period hasexpired since the last received warning for the trunk zone. The warningtime period may be configured by a user to a desired length. If thewarning time period has expired, this may indicate an intrusion attempton a separate zone in addition to an intrusion attempt on the trunk zoneand the system proceeds to 809 to evaluate the alert as a standard zoneand returns to step 711.

If the system determines in 803 that the warning time period has notexpired, this may indicate that there is an alert in a zone inconjunction with the trunk zone and the system proceeds to 804. In 804,the system determines if the zone warning mode has been set to apredetermined setting. In one embodiment, the predetermined setting maybe ‘Warning with Trunk Zone’. In one embodiment, if the zone does nothave a warning mode of ‘Warning with Trunk Zone’ 804, the system setsthe warning mode to ‘Warning with Trunk Zone’ in 805 prior to movingonto 806. In 806, the system evaluates if all zones in the zone's zonegroup have warning modes set to ‘Warning with Trunk Zone’. In onescenario, if a cable in a riser closet is disturbed, the trunk cable andall of the cables that are monitoring the floors below will set offalerts. In this case, the floor cables will have a ‘Warning with TrunkZone’ status so the system can separate these from a user zone. If not,the system proceeds to 809 to evaluate the alert as a standard zone andreturns to step 711.

If all zones in the zone's zone group have warning modes set to ‘Warningwith Trunk Zone’, this may indicate that the entire zone group hasreceived alerts in conjunction with the trunk zone. In that instance,the system will not evaluate the alert as a standard zone, but insteadthe system may suppress it. The system then proceeds to 807 to determineif the zone is set to active status. If not, the system sets the zone toactive status in 808 and proceeds to continue to alert processing. Whilethe flowchart shown in FIG. 8 and described herein depicts an exemplaryworkflow for a trunk cable processing sub process, other workflowsarranged in a different order may be implemented.

Turning to FIG. 9, a flowchart for ‘create alarm’ sub process 900according to an embodiment is shown. A system may create an alarmaccording to ‘create alarm’ sub process 900 when a zone receives aboundary alert, when a zone receives multiple warnings above a criteria,or when a zone warning count exceeds a defined threshold for the zone.In 901, a system evaluates if a zone is a trunk zone. If the zone is atrunk zone, the system may retrieve the highest consecutive zone groupwith a warning mode of ‘Warning with Trunk Zone’ in 902. A system mayindicate this information in a case as described in more detail below.

A system may create and opens a case in 903. If a case was opened due toa boundary alert, a system may notate the case accordingly. In 904, asystem may notify a personnel related to a zone. If a case was openeddue to a boundary alert, a system may notate the notificationaccordingly. In 905, a system may determine if a zone is configured todisable data. If yes, the system may perform a disable data sub process1000. In 906, a system may determine if a zone is configured to update aphysical security device. If yes, the system may perform the actionbased on a zone setting by sending a command to the physical securitydevice management platform in 907. In 908, a system may determine if azone is configured to re-route network data. If yes, the systemre-routes data based on a zone setting by sending a command to anoptical circuit switch in 909. In 910, a system may determine if a zoneis configured to perform network analysis. If yes, the system performsan action based on a zone setting by sending a command to an opticaltest access point in 911. A system may communicate with a networkanalytic tool based on a defined action. While the flowchart shown inFIG. 9 and described herein depicts an exemplary workflow for a createalarm sub process, other workflows arranged in a different order may beimplemented.

In FIG. 10, a flowchart for ‘disable data’ sub process 1000 according toan embodiment is shown. In 1001, a system may evaluate a zone type. In1002, if a zone is an outside plant zone, the system may collect allzones in a same data zone as the outside plant zone. The system may thenproceeds to 1006 to disable data in all of these zones.

In 1003, a system may evaluate if a zone is a trunk zone. If yes, thesystem collects all zones up to and including the highest consecutivezone group with a warning mode of ‘Warning with Trunk Zone’ in 1004. Thesystem may then proceeds to 1006 to disable data in all of these zones.In 1003, if a system determines that a zone is not a trunk zone but is auser zone, the system may retrieve the current zone in 1005 and proceedto disable data in this zone in 1006.

A system may be configured to disable data by directly communicatingwith an optical line terminal and/or network switch by sending a commandto the optical line terminal and/or network switch. A system may also beconfigured to disabled data by communicating with an optical circuitswitch by sending a command to the optical circuit switch. While theflowchart shown in FIG. 10 and described herein depicts an exemplaryworkflow for a disable data sub process, other workflows arranged in adifferent order may be implemented.

Turning to FIG. 11, a work flow for processing open warnings 1100according to an embodiment is shown. In 1101, on a defined interval, asystem may open all active warnings. In 1102, a system may determine ifa warning time period has elapsed since last receiving a warningtimestamp. If the warning time period has not elapse, the system mayproceed to 1103 and wait for a defined interval before returning tocheck all active warnings. If the warning time period has elapsed, thesystem may proceed to 1104 to determine if a zone is a trunk zone. Ifthe zone is not a trunk zone, the system may proceed to 1107 and closean active warning. If the zone is a trunk zone, the system may collectall zones up to and including the highest consecutive zone group with awarning mode of ‘Warning with Trunk Zone’ in 1105 and may then proceedto 1106. In 1106, a system may check if the trunk zone is alarmed. Ifnot, the system may close the active warning in 1107. In 1108, a systemmay set a zone warning count to zero. In 1109, a system may set a zonestatus to active monitoring. While the flowchart shown in FIG. 11 anddescribed herein depicts an exemplary workflow for processing openwarnings, other workflows arranged in a different order may beimplemented.

FIG. 12 shows a case resolution process according to an embodiment. In1203, when a case is created, a zone monitor 1201 may open the case andreview the case details. The case details displayed by a system mayinclude warning count, zone type, zone images, zone inspection guide,notified contact personnel, and status of the data network. A casedetail screen according to one embodiment is shown in FIG. 13.

In 1204, zone monitor 1201 may dispatch an investigator 1202 assigned toa zone. In 1206, zone monitor 1201 may record zone investigator's 1202name. In 1205, zone investigator 1202 may investigate a zone based on aStandard Operating Procedure defined by a system for a zone. In 1207,zone investigator 1202 may document evidence such as images or videos ofthe inspection. In 1208, upon completion of an investigation, zoneinvestigator 1202 may relay a full report in back to zone monitor 1201,including investigation evidence, a written report, and a finaldetermination. Final determinations may include items such as intrusion,accidental contact, unscheduled maintenance, natural disaster, and otheritems.

In 1209, zone monitor 1201 may record zone investigator's 1202 reportinto a system. In 1210, a system may enable zone monitor 1201 to resetmonitoring on a zone.

In 1211, when zone monitor 1201 resets monitoring on a zone, a systemmay check to see if data was disabled in a zone. If so, the system mayallow zone monitor 1201 to restore data to the zone in 1212. Zonemonitor 1201 may then restore data to the zone.

In 1213, a system may then close a case and track a time stamp for eachevent for audit and reporting purposes. While the workflow for a caseresolution process as shown in FIG. 12 and described herein depicts anexemplary workflow, other workflows arranged in a different order may beimplemented.

In an embodiment, when a case is open and under review, a system maycontinue to monitor for new alerts in a zone. FIG. 14 shows a flowchart1400 of a process for a system to continue monitoring during a casemanagement. In 1401, a system may determine if a new alert is detectedin a zone. In 1402, if a new alert is detected, the system may update aninterface with visual and audible indicators, such as an Eagle Eye Zonarwarning. This scenario may occur if an intrusion attempted iscontinuing. This process may provide an investigator situationalawareness and allow for additional safety or response measures.

In 1403, a system may require a user to notify an investigator of theEagle Eye Zonar warning. In 1404, a system may determine if a user hasnotified an investigator. If not, the system may return to 1403 torequire a user to notify an investigator. In 1405, after a user notifiesan investigator, the system may update a case note with information andtimestamp for the Eagle Eye warning detection and user acknowledgement.In 1406, a system may then allow a user to continue with a caseresolution process. While the flowchart shown in FIG. 14 and describedherein depicts an exemplary workflow for a process to continuemonitoring during a case management, other workflows arranged in adifferent order may be implemented.

According to an embodiment, a system may allow a user with anappropriate privilege the ability to modify a case resolution workflow.A system may allow for adding or removing steps into a workflow. Asystem may allow for routing and re-routing approval or disapprovalfunctions to a user, collection of users, roles or a collection of rolesin a system. Where appropriate, a system may allow for modification of aworkflow through a graphically based user interface.

In one embodiment, a system may be configured for predictive analysis. Asystem may calculate the captured alert signatures (duration, count,maximum/minimum/average power, etc.) for a case as well as an associatedcase resolution status. A system may provide artificial intelligencecapabilities in analyzing an alert signature and a resolution to computelikelihood scores for possible causes for an alert.

For a case, a system may use a predictive analysis to offer likelihoodscores on the case resolutions status. For each warning, a system mayprovide a real-time likelihood score for a cause of an alert.

Other features of a system may provide the ability to continuouslymonitor a given IP address range to discover and enroll unregisteredintrusion detectors. A system may allow a user to create a newenrollment task. An enrollment task may include:

-   -   Starting IP Address    -   Ending IP Address    -   Login ID for Intrusion Detector    -   Password for Login ID for Intrusion Detector    -   Frequency at which the Enrollment Task should run (Never, Daily,        Weekly)    -   SNMP Credentials for communication with the Intrusion Detector    -   Option to All Remote Reset of the Channel Ports of the Intrusion        Detector    -   Option to Disable Data in the Zones when an Alarm occurs    -   Warning Threshold Count    -   Warning Threshold Time Period    -   Alarm Response for Intrusion Alerts (None, Report, Report &        Halt, Halt)    -   Alarm Response for Boundary Alerts (None, Report, Report & Halt,        Halt)    -   Alarm Response for Smart Filter Detect Alerts (None, Report,        Report & Halt, Halt)    -   Device Availability Time Period

During enrollment, a system may query a discovered device and gatherdevice specific information such as the model and the port count of thedevice. A system may use the information to dynamically enroll thedevice. A system may provide the ability to discover a variety of devicemodels and types from one enrollment task.

After enrollment completes, a system may read an intrusion detectorthreshold setting. A system may disable monitoring on channel ports thatare determined to not have a fiber cable plugged into it. A system mayprovide a wizard based workflow to allow a user to provide additionalinformation to configure an enrolled device.

According to another embodiment, a system may provide the ability to seta specific channel port on an intrusion detector into a Learning Mode orAuto Configure. In this mode, an intrusion detector observes a fiber fora channel port for a configurable period of time to determine an optimalmonitoring parameter that may be used for monitoring intrusions,excessive optical gains/losses or environmental changes.

A system may be configured to allow a user with an appropriate privilegean option to perform Learning Mode. When the option is selected, thesystem may present an allowed user with a screen offering various timeperiods. When a user initiates a task in a system, the system sends anappropriate command to an intrusion detector to begin Learning Mode. Asystem may set the channel port Report only for any alert and not sendHalt alerts. At any time during Learning Mode, a system may allow a userto abort Learning Mode. A system may continue to receive a detectedalert during Learning Mode and may record the results in the system forfurther consideration by a user.

When Learning Mode completes, a system may receive a notification froman intrusion detector. A system may read and record a threshold settingdetermined during Learning Mode and associate the setting to a specificzone. A system may reset a channel port back from Report only to aprevious setting.

A system may read and record a current threshold setting of a channelport of an intrusion detector and associate the setting to a specificzone. For a setting, a system may indicate if the setting was Learned,set by Default, or set by a User.

A system may allow a user with an appropriate privilege the ability tosync a setting from a device to a system. A system may allow a user withan appropriate privilege the ability to edit any or all of the settings.When a user initiates a task in a system to update a setting, the systemmay send an appropriate command to an intrusion detector to update thesettings based on the user provided values. Any settings unchanged by auser remain unaffected.

A system may be deployed for various purposes. In one embodiment, asystem may be used to verify whether a data infrastructure is suitablefor alarmed carrier PDS. This testing process maybe used pre-deploymenton existing cables and conduit or during post-deployment testing processto validate new installations of alarmed cables and conduit.

FIG. 15 shows a system 1500 for facilitating detection of a disturbanceon an information transmission line, in accordance with one or moreembodiments. As shown in FIG. 15, system 1500 may include server(s)1502, client device 1504 (or client devices 1504 a-1504 n), network1550, database 1532, sensors 1522, physical transmission line 1526,visual indication 1528, and/or other components. Server 1502 may includedisturbance identifying subsystem 1512, communication sub system 1514,presentation sub system 1516, updating sub system 1518, and/or othercomponents. Each client device 1504 may include any type of mobileterminal, fixed terminal, or other device. By way of example, clientdevice 1504 may include a desktop computer, a notebook computer, atablet computer, a smartphone, a wearable device, or other clientdevice. Users may, for instance, utilize one or more client devices 1504to interact with one another, one or more servers, or other componentsof system 1500. It should be noted that, while one or more operationsare described herein as being performed by particular components ofserver 1502, those operations may, in some embodiments, be performed byother components of server 1502 or other components of system 1500. Asan example, while one or more operations are described herein as beingperformed by components of server 1502, those operations may, in someembodiments, be performed by components of client device 1504. Further,although the server 1502, client device 1504, sensors 1522, physicaltransmission line 1526, visual indication 1528, and database 1532 areillustrated as being separate and connected via network 1550, it shouldbe understood that one or more of the server 1502, client device 1504,sensors 1522, physical transmission line 1526, visual indication 1528,and database 1532 may be co-located. Further, although the database 1532is illustrated as being separate from the server 1502 and the clientdevice 1504, the database 1532 may be located within the client device1504 and/or server 1502. One or more components (and their functions) ofthe systems illustrated in FIGS. 1 and 2 may correspond to one or morecomponents (and their functions) of the systems illustrated in FIGS. 15,33, and 34, and vice versa. Further, one or more functions describedabove with regard FIGS. 1-14 may be performed by one or more componentsof the systems illustrated in FIGS. 15, 17, 19, 20, 33, and 34. One ormore functions described below with regard to FIGS. 15-34 may beperformed by one or more components of the systems illustrated in FIGS.1 and 2.

Sensor-Based Disturbance Detection and Shutdown of Network Data Flow

In some embodiments, server 1502, via sensors 1522, may monitor thephysical transmission line 1526 (e.g., a fiber optic informationtransmission line). As an example, FIG. 7 describes a system that maykeep an open port to listen for an alert (see step 701 in FIG. 7).Further, in some embodiments, system 1500 may detect, via one or moresensors 1522, a disturbance on a physical transmission line, where thedetected disturbance does not exceed a first present threshold fortriggering alerts of a first alert type. With respect to FIG. 7, forexample, a system may determine whether a zone has multiple warningsthat meet one or more predefined criteria (see step 704 in FIG. 7).System 1500 may also detect, via one or more sensors 1522, a disturbanceon the physical transmission line, wherein the detected disturbance doesnot exceed a first preset threshold for triggering a network data flowshutdown response. With respect to FIG. 2, for example, a system maydisable or re-route data by sending a command to a networking equipmentusing data port address in the event of an intrusion attempt. The systemmay enable or disable data on a specific port and obtain details for theport.

Additionally, in some embodiments, the system 1500 (e.g., server 1502)may determine, responsive to the detection via the sensor 1522, a countfor a number of disturbances within a preset time period that do notexceed the first preset threshold and determine, whether the count, forthe number of disturbances that do not exceed the first presetthreshold, exceeds a second preset threshold, wherein the second presetthreshold corresponds to a preset number of allowable disturbances, notexceeding the first preset threshold and within the preset time period,before one or more alerts of the first alert type are to be triggered.Further, in some embodiments, an alert may be triggered of a first typeresponsive to a determination that the count exceeds the second presetthreshold. With respect to FIG. 7, for example, a warning counter mayincrement a warning count for a zone when it is determined that the zonedoes not have multiple warnings that meet one or more predefinedcriteria (see steps 704, 705, 707, and 708 in FIG. 7), and an alarm maybe triggered when the warning count exceeds a predefined threshold (seesteps 711 and 900 in FIG. 7). Also, in some embodiments, the networkdata may be caused to be shut down to one or more network endpointsproximate to the detected disturbance on the physical transmission lineresponse to a determination that the count exceeds the second presetthreshold. As discussed, for example, a system may disable or re-routedata by sending a command to a networking equipment using data portaddress in the event of an intrusion attempt. The system may enable ordisable data on a specific port and obtain details for the port.

Disturbance Location and/or Type Identification

In some embodiments, system 1500 may identify a location of adisturbance on a physical transmission line. Server 1502 may obtainsensor data from sensors 1522 located on a physical transmission line1526 (e.g., obtain first sensor data from a first sensor and secondsensor data from a second sensor). The sensors 1522 may be opticalsensors, electrical sensors, acoustical sensors, and/or fiber bragggrating (FBG) sensors and may be placed at different locations of thephysical transmission line 1526. These sensors 1522 may be capable ofdetecting one or more disturbance events that occur on or near thephysical transmission line 1526. For example, the optical sensors may beable to detect optical disturbance events, the electrical sensors may beable to detect electrical disturbance events, and the acoustical sensorsmay be able to detect acoustical disturbance events. Although onlyoptical sensors, electrical sensors, acoustical sensors, and/or fiberbragg grating (FBG) sensors are discussed above, it should be understoodthat one or more other types of sensor may be used to detect disturbanceevents on the physical transmission line 1526. The sensor data may bereceived by the server 1502 from the sensors 1522 on a continuous basisor may be received upon request. Continuous reception of the sensor datafrom the sensors 1522 may allow the system 1500 to continuously monitorthe physical transmission line 1526 and identify a location of adisturbance event on the physical transmission line 1526. The sensordata received from the sensors 1522 may include measured values of oneor more disturbance events (e.g., first sensor data from a first sensormay include first measured values of the disturbance event, secondsensor data from a second sensor may include second measured values ofthe disturbance event, etc.) over a length of time. For example, FIG. 16illustrates sensor data obtained from a sensor (from among sensors 1522)that includes peaks and valleys (e.g., measured values of a disturbanceevent) over a length of time. These peaks and valleys over the length oftime illustrate an occurrence of a disturbance event and these peaks andvalleys can be used to identify a location of the disturbance event anda type of the disturbance event.

In some embodiments, the sensors 1522 may be located at predeterminedpositions on the physical transmission line 1526. Information regardingthe location of the sensors 1522 on the physical transmission line 1526may be stored in a sensor database 1536. In addition to the informationregarding the location of the sensors 1522, information regarding thedistances between these sensors 1522 may also be stored in the sensordatabase 1526. FIG. 17 illustrates a physical transmission line (seepipe sections #1, #2, and #3) and sensors (see sensors S1, S2, S3, andS4) placed at different locations on the physical transmission line. Thedistance between sensors S1 and S2 may be equal to the distance betweensensors S3 and S2 (and S2 and S4). Alternatively, the distances betweenadjacent sensors may be different. When sensors measure disturbanceevents (e.g., based on detected disturbance events), server 1502 (via,for example, communication subsystem 1514) may obtain sensor data thatincludes measured values of the disturbance events over a length oftime. For example, FIG. 18 illustrates sensor data 1801, 1802, and 1803obtained from sensors S1, S2, and S3, respectively. The sensor data1801, 1802, and 1803 may include measured values (e.g., as measured ingain or loss in optical power, acoustical power, and/or electricalresistance) of a disturbance event over a length of time. The measuredvalues may correspond to either light or sound disturbances (e.g.,changes in ambient environmental conditions) that the sensors maydetect. Sensor data 1801 may include measured values of a disturbanceevent by sensor S1, sensor data 1802 may include measured values of thesame disturbance event by sensor S2, and sensor data 1803 may includemeasured values of the same disturbance event by sensor S3. For example,when there is a disturbance event, more than one sensor may detect thedisturbance event and output its own corresponding sensor data. Thesensor data 1801, 1802, and 1803 that include measured values of adisturbance event by the sensors S1, S2, and S3, respectively, maycorrespond to a single disturbance event or multiple differentdisturbance events.

In some embodiments, the server 1502 (e.g., disturbance identifyingsubsystem 1512) may determine an initial detection time of the measuredvalues based on the obtained sensor data (or a portion of the obtainedsensor data). For example, server 1502 may determine a first initialdetection time T1 of the first measured values (see sensor data 1801 inFIG. 18), a second initial detection time T2 of the second measuredvalues (see sensor data 1802 in FIG. 18), and a third initial detectiontime T3 of the third measured values (see sensor data 1803 in FIG. 18).Additionally or alternatively, the server 1502 may determine otherdetection times. For example, server 1502 may determine detection timesT4, T5, and T6 (see broken line of box 1810 intersecting sensor data1801, 1802, and 1803) of the first measured values (see sensor data 1801in FIG. 18), the second measured values (see sensor data 1802 in FIG.18), and the third measured values (see sensor data 1803 in FIG. 18),respectively, based on the obtained sensor data 1801, 1802, and 1803.The server 1502 (e.g., disturbance identifying subsystem 1512) maydetermine a time difference between detections times (e.g., differencebetween T1 and T2, T2 and T3, T1 and T3, T4 and T5, T5 and T6, and/or T4and T6) and may approximate (i) a first distance between the disturbanceevent and the first sensor based on a determined time difference, aknown constant (e.g., speed of sound and/or speed of light), and a knownlength of the physical transmission line (or a section of the physicaltransmission line), (ii) a second distance between the disturbance eventand the second sensor based on a determined time difference, the knownconstant, and a known length of the physical transmission line (or asection of the physical transmission line), and (iii) a third distancebetween the disturbance event and the third sensor based on a determinedtime difference, the known constant, and a known length of the physicaltransmission line (or a section of the physical transmission line).

The server 1502 (e.g., disturbance identifying subsystem 1512) mayidentify a location of the disturbance event on the physicaltransmission line based on the approximated distances of the sensorsfrom the disturbance event. In addition, the location of the disturbanceevent on the physical transmission line may be identified further basedon locations of these sensors on the physical transmission line. Forexample, the server 1502 may retrieve the information regarding thelocation of the sensors from the sensor database 1536 and utilize thisinformation to identify the location of the disturbance event on thephysical transmission line. Additionally, the server 1502 may retrieveinformation regarding the distance between the sensors from the sensordatabase 1536 and utilize this information to identify the location ofthe disturbance event on the physical transmission line. Although theexample provided above describes three sensors and three sensor data, itshould be understood that a location of the disturbance event on thephysical transmission line may be identified based on sensor dataobtained from two sensors. In summary, the system 1500 may use timedifference (e.g., time of flight) between sensor data of differentsensors to determine and identify a location of the disturbance event onthe physical transmission line. Additionally, the server 1502 (forexample disturbance identifying subsystem 1512) may compare the sensordata 1801, 1802, and 1803 to each other (e.g., by comparing the timedurations of the sensor data, peak/valley magnitudes of the sensor data,etc.) to determine whether the sensor data 1801, 1802, and 1803correspond to a single disturbance event or multiple differentdisturbance events on the physical transmission line. For example, inFIG. 18, the comparison of the sensor data 1801, 1802, and 1803 withinbox 1810 suggests that the sensor data 1801, 1802, and 1803 correspondto a single disturbance event.

Further, in some embodiments, the location of a disturbance event on aphysical transmission line (e.g., a sensing fiber) may bedetermined/identified using a sensing device 1900 (e.g., a circuit ormeter that reads resistance and/or current, or an optical interrogator)and a sensor 1903 (e.g., a fiber bragg grating (FBG) sensor) illustratedin FIG. 19. The sensing device 1900 may be connected to the sensor 1903via a port/channel and may acquire data sensed by the sensor 1903.

FIG. 19 illustrates a sensing device 1900 that emits a beam of light1901 to a reflecting sensor 1903 via the sensing fiber 1906, and basedon the sensor 1903, a specific and known wavelength of light 1904 isreflected via the sensing fiber 1906. A disturbance event on the sensingfiber 1906 may alter the reflected light's wavelength, amplitude, and/orother properties of light along distance B (e.g., 1905 in FIG. 19). Thesensing device 1900 may gather sensing data based on the reflected light1904. The sensing data may include information regarding timestampvalues assigned to a light beam 1901 emitted by the sensing device 1900and reflected back (e.g., light 1904) to the sensing device 1900 by thesensor 1903 and information regarding a property of the light beam 1904reflected back to the sensing device 1900. The sensing device 1900 mayprovide the sensing data to the server 1502 (based on a wired orwireless connection between the server 1502 and the sensing device1900). The server 1502 may then calculate a roundtrip time of the lightbeam 1901 emitted by the sensing device 1900 and reflected back (e.g.,light 1904) to the sensing device 1900 by the sensor 1903 based on theassigned timestamp values. Further, the server 1502, based on thereceived sensing data from the sensing device 1900, may determine achange in properties of the light beam 1901 emitted by the sensingdevice 1900 and reflected back (e.g., light 1904) to the sensing device1900 by the sensor 1903 by comparing the properties (e.g., amplitude,frequency, wavelength, power variance, etc.) of the reflected light beam1904 to the properties of a known light beam that is reflected by sensor1903 with and/or without a disturbance event on the sensing fiber 1906.In other words, the sensing device 1900 may provide raw data to theserver 1502, and the server 1502 may calculate the roundtrip time anddetermine the change in properties based on such raw data.Alternatively, the sensing device 1900 may calculate the roundtrip timeof the light beam 1901 emitted by the sensing device 1900 and reflectedback (e.g., light 1904) to the sensing device 1900 by the sensor 1903based on the assigned time stamp values. Also, alternatively, thesensing device 1900 may determine the change in properties of the lightbeam 1901 emitted by the sensing device 1900 and reflected back (e.g.,light 1904) to the sensing device 1900 by the sensor 1903 by comparingthe properties (e.g., amplitude, frequency, wavelength, power variance,etc.) of the reflected light beam 1904 to the properties of a knownlight beam that is reflected by sensor 1903 with and/or without adisturbance event on the sensing fiber 1906. The properties of knownlight beams may be stored in the database 1532 and may be retrieved bythe server 1502 and/or sensing device 1900 for comparisons with thereflected light beam 1904

Based on the sensing data, the server 1502 (e.g., the disturbanceidentifying subsystem 1512) may identify the location of the disturbanceevent on the physical transmission line. In other words, the server 1502may identify the location of the disturbance event on the physicaltransmission line 1906 (and may identify the distance of the disturbanceevent from the sensing device 1900) based on the roundtrip time of thelight beam 1901 emitted by the sensing device 1900 and reflected back(e.g., light 1904) to the sensing device 1900 by the sensor 1903 and thechange in the property (or multiple properties) of the light beam 1901emitted by the sensing device 1900 and reflected back (e.g., light 1904)to the sensing device 1900 by the sensor 1903. The server 1502 may alsobe able to determine a length of the distance event (e.g., start and endlocations of the disturbance event) based on the comparison of theproperties (e.g., wavelength, power variance, etc.) of the reflectedlight beam 1904 to the properties of a known light beam that isreflected by sensor 1903 with and/or without a disturbance event on thesensing fiber 1906. For instance, the wavelength of the reflected lightbeam 1904 may be compared to a baseline wavelength to determine startand end locations of the disturbance event on the physical transmissionline. Also, the power variance of the reflected light beam 1904 may becompared to a baseline power variance to determine start and endlocations of the disturbance event on the physical transmission line.Further, the detection times of the start and end of peaks and valleysof the sensor data (along with a known constant) may also be used todetermine the start and end locations of the disturbance event on thephysical transmission line. Alternatively, the sensing device 1900,based on the sensing data, may identify the location of the disturbanceevent on the physical transmission line 1906 (and may identify thedistance of the disturbance event from the sensing device 1900) based onthe roundtrip time of the light beam 1901 emitted by the sensing device1900 and reflected back (e.g., light 1904) to the sensing device 1900 bythe sensor 1903 and the change in the property (or multiple properties)of the light beam 1901 emitted by the sensing device 1900 and reflectedback (e.g., light 1904) to the sensing device 1900 by the sensor 1903.Also, alternatively, the sensing device 1900 may determine a length ofthe distance event (e.g., start and end locations of the disturbanceevent) based on the comparison of the properties (e.g., wavelength,power variance, etc.) of the reflected light beam 1904 to the propertiesof a known light beam that is reflected by sensor 1903 with and/orwithout a disturbance event on the sensing fiber 1906. The properties ofknown light beams may be stored in the database 1532 and may beretrieved by the server 1502 and/or sensing device 1900 for comparisonswith the reflected light beam 1904.

Although only one sensor is illustrated in FIG. 19, it should beunderstood that multiple sensors may be used and sensing data from eachsensor may be gathered by the sensing device 1900. Additionally, morethan one sensing device 1900 may be placed at different locations of thephysical transmission line to gather sensing data, which may then beobtained by the server 1502. The known distances A (see 1902 in FIG. 19)and B (see 1905 in FIG. 19), a known constant (e.g., speed of lightand/or sound), and time resolution capabilities of the sensing device1900 can be taken into account to identify the location of thedisturbance event on the physical transmission line. Additionally, thelocation of the disturbance event on the physical transmission line maybe identified further based on a location of the sensing device on thephysical transmission line. The information regarding a location of oneor more sensing devices on the physical transmission line may be storedin the sensor database 1536, and such information may be retrieved by,for example, the server 1502 and/or the sensing device 1900.

Further, in some embodiments, the location of a disturbance event on aphysical transmission line (e.g., a sensing fiber) may bedetermined/identified using a sensing device 2000 (e.g., a circuit ormeter that reads resistance and/or current, or an optical interrogator)and sensors 2004 and 2005 (e.g., fiber bragg grating (FBG) sensors)illustrated in FIG. 20. The sensors 2004 and 2005 may be connected tothe sensing device 2000 either individually or in series to aport/channel on the sensing device 2000, and the sensing device 2000 mayacquire data sensed by the sensors 2004 and 2005.

FIG. 20 illustrates a sensing device 2000 that emits a beam of light2001 to a reflecting sensor 2004 via a sensing fiber 2009, and based onthe sensor 2004, a specific and known wavelength of light 2006 isreflected via the sensing fiber 2009. A disturbance event on the sensingfiber 2009 may alter the reflected light's wavelength, amplitude, and/orother properties of light along distance B (e.g., 2008 in FIG. 20).Further, the sensing device 2000 may emit another beam of light 2002(e.g., this may be a time source signal such as an alternating beam oflight at a specific interval) that is reflected (see 2007 in FIG. 20)against another sensor 2005 at an alternate wavelength from the lightbeam 2001 and/or 2006. The other beam of light 2002 may be emitted viathe sensing fiber 2009 and reflected (see 2007 in FIG. 20) back to thesensing device 2000 via the sensing fiber 2009. The sensing device 2000may gather sensing data based on the reflected light 2006 and 2007. Thesensing data may include information regarding a change in a property ofthe light beam 2001 emitted by the sensing device 2000 and reflectedback (e.g., light 2006 in FIG. 20) to the sensing device 2000 by sensor2004 and information regarding timestamp values assigned to light beam2002 emitted by the sensing device 2000 and reflected (e.g., light 2007)back to the sensing device 2000 by sensor 2005. The sensing device 2000may provide the sensing data to the server 1502 (based on a wired orwireless connection between the server 1502 and the sensing device2000).

The server 1502 may then calculate a roundtrip time of the light beam2002 emitted by the sensing device 2000 and reflected back (e.g., light2007) to the sensing device 2000 by sensor 2005 based on the assignedtimestamp values. The time source signal (see 2002 and 2007 in FIG. 20)may be used to establish a timing sequence, which based on a knowndistance can establish an internal timestamp that correlates to thedetected light properties used for disturbance detection. Further, theserver 1502, based on the received sensing data from the sensing device2000, may determine the change in properties of the light beam 2001emitted by the sensing device 2000 and reflected back (e.g., light 2006)to the sensing device 2000 by sensor 2004 by comparing the properties(e.g., amplitude, frequency, wavelength, power variance, etc.) of thereflected light beam 2006 to the properties of a known light beam thatis reflected by sensor 2004 with and/or without a disturbance event onthe sensing fiber 2009. In other words, the sensing device 2000 mayprovide raw data to the server 1502, and the server 1502 may calculatethe roundtrip time and determine the change in properties based on suchraw data. Alternatively, the sensing device 2000 may calculate theroundtrip time of the light beam 2002 emitted by the sensing device 2000and reflected back (e.g., light 2007) to the sensing device 2000 bysensor 2005 based on the assigned timestamp values. Also, alternatively,the sensing device 2000 may determine the change in properties of thelight beam 2001 emitted by the sensing device 2000 and reflected back(e.g., light 2006) to the sensing device 2000 by sensor 2004 bycomparing the properties (e.g., amplitude, frequency, wavelength, powervariance, etc.) of the reflected light beam 2006 to the properties of aknown light beam that is reflected by sensor 2004 with and/or without adisturbance event on the sensing fiber 2009. The properties of knownlight beams may be stored in the database 1532 and may be retrieved bythe server 1502 and/or sensing device 2000 for comparisons with thereflected light beam 2006.

Based on the sensing data, the server 1502 (e.g., the disturbanceidentifying subsystem 1512) may identify the location of the disturbanceevent on the physical transmission line. In other words, the server 1502may identify the location of the disturbance event on the physicaltransmission line 2009 (and may identify the distance of the disturbanceevent from the sensing device 2000) based on the roundtrip time of thelight beam 2002 emitted by the sensing device 2000 and reflected back(e.g., light 2007) to the sensing device 2000 by the sensor 2005 and thechange in the property (or multiple properties) of the light beam 2001emitted by the sensing device 2000 and reflected back (e.g., light 2006)to the sensing device 2000 by the sensor 2004. The server 1502 may alsobe able to determine a length of the distance event (e.g., start and endlocations of the disturbance event) based on the comparison of theproperties (e.g., wavelength, power variance, etc.) of the reflectedlight beam 2006 to the properties of a known light beam that isreflected by sensor 2004 with and/or without a disturbance event on thesensing fiber 2009. For instance, the wavelength of the reflected lightbeam 2006 may be compared to a baseline wavelength to determine startand end locations of the disturbance event on the physical transmissionline. Also, the power variance of the reflected light beam 2006 may becompared to a baseline power variance to determine start and endlocations of the disturbance event on the physical transmission line.Alternatively, the sensing device 2000, based on the sensing data, mayidentify the location of the disturbance event on the physicaltransmission line 2009 (and may identify the distance of the disturbanceevent from the sensing device 2000) based on the roundtrip time of thelight beam 2002 emitted by the sensing device 2000 and reflected back(e.g., light 2007) to the sensing device 2000 by the sensor 2005 and thechange in the property (or multiple properties) of the light beam 2001emitted by the sensing device 2000 and reflected back (e.g., light 2006)to the sensing device 2000 by the sensor 2004. Also, alternatively, thesensing device 2000 may determine a length of the distance event (e.g.,start and end locations of the disturbance event) based on thecomparison of the properties (e.g., wavelength, power variance, etc.) ofthe reflected light beam 2006 to the properties of a known light beamthat is reflected by sensor 2004 with and/or without a disturbance eventon the sensing fiber 2009. The properties of known light beams may bestored in the database 1532 and may be retrieved by the server 1502and/or sensing device 2000 for comparisons with the reflected light beam2006.

Although only two sensors are illustrated in FIG. 20, it should beunderstood that more than two sensors may be used and sensing data fromeach sensor may be gathered by the sensing device 2000. Additionally,more than one sensing device 2000 may be placed at different locationsof the physical transmission line to gather sensing data, which may thenbe obtained by the server 1502. The known distances A (see 2003 in FIG.20) and B (see 2008 in FIG. 20), a known constant (e.g., speed of lightand/or sound), and internal timestamps can be taken into account toidentify the location of the disturbance event on the physicaltransmission line. Additionally, the location of the disturbance eventon the physical transmission line may be identified further based on alocation of the sensing device on the physical transmission line. Theinformation regarding a location of one or more sensing devices on thephysical transmission line may be stored in the sensor database 1536,and such information may be retrieved by, for example, the server 1502and/or the sensing device 2000.

The identified location of the disturbance event may bepresented/displayed to a user via a user interface (see presentationsubsystem 1516 in FIG. 15). As illustrated in FIG. 21, a location 2100of a disturbance event can be identified on a physical transmission linethat includes a plurality of sensors S1, S2, S3, and S4. The userinterface may also present/display the identified location of thedisturbance event as a location 2104 within a building and/or a location2103 within a floor plan. The user interface may also present/display atype of the disturbance event. For example, in FIG. 21, the disturbanceevent is identified as a potential hammer tap (see 2101 in FIG. 21). Theuser interface may request a user to confirm the accuracy (via buttons2102 in FIG. 21) of the identified type of disturbance event.

When a location of the disturbance event is identified, the server 1502(e.g., communication subsystem 1514) may communicate a signal to thephysical transmission line. Such a signal may disable (or cause shutdown of) a portion of the physical transmission line that includes thedisturbance event and re-route the information transmitted via thephysical transmission line such that the portion of the physicaltransmission line that includes the disturbance event does not transmitthe information. For example, as noted above, the server 1502 may beable to determine a length of the disturbance event (e.g., start and endlocations of the disturbance event) based on the comparison of theproperties (e.g., wavelength, power variance, etc.) of a reflected lightbeam (see FIGS. 19 and 20) to the properties of a known light beam thatis reflected by sensor with and/or without a disturbance event on asensing fiber. Based on the length of the disturbance event on thephysical transmission line, the server 1502 may determine which portionof the physical transmission line needs to be disabled (e.g.,temporarily) and determine a new route for the transmission ofinformation via the physical transmission line. It should be understoodthat only a specific portion of the physical transmission line (e.g.,the portion corresponding to the identified location of the disturbanceevent) may be disabled, while other portions of the physicaltransmission line may be allowed to function normally (e.g., otherportions of the physical transmission line where no disturbance eventhas been identified).

In some embodiments, system 1500 may identify a type of a disturbanceevent on a physical transmission line based on a comparison of theobtained sensor data and stored signature data. Signature data maycorrespond to previous disturbance events and may include previouslymeasured values over a length of time. Signatures files that includesignature data may be stored in a signature database 1534 and may beretrieved by the server 1502. The server 1502 may obtain (via, forexample, the communication subsystem 1514) signature files correspondingto previous disturbance events from the signature database 1534. Each ofthe signature files may include signature data including previouslymeasured values of the previous disturbance events over a length oftime. For example, a first signature file may correspond to a hammertap, a second signature file may correspond to a drill, a thirdsignature file may correspond to a human voice, etc. FIG. 22 illustratesa hammer tap 2200 (which results in hammers sounds) on a physicaltransmission line (which includes a plurality of sensors S1, S2, andS3), which results in the generation of sensor data 2201 by one of thesensors. A signature file including a portion of the sensor data 2202and other data 2203 may be generated based on the sensor data 2201 andthe signature file may be stored in the signature database 1534.

The server 1502 (e.g., disturbance identifying subsystem 1512) maycompare sensor data (which may be obtained from sensors 1522) andsignature data of the signature files obtained from the signaturedatabase 1534 and based on such a comparison, the server 1502 (e.g.,disturbance identifying subsystem 1512) may determine a confidence valuefor each of the signature files based on the comparison of the sensordata with the signature data of the signature files. For example, if theobtained sensor data includes first sensor data 1801, second sensor data1802, and third sensor data 1803 (see FIG. 18), the server 1502 maycompare the first, second, and third sensor data with the signature dataof the signature files, and determine a confidence value for each of thesignature files based on the comparison of the first, second, and thirdsensor data with the signature data of the signature files.

For instance, comparing first sensor data with the signature data of thesignature files may include determining, for each of the signaturefiles, a first total number of overlapping values between the firstsensor data and the signature data of the signature file, determining,for each of the signature files, a first total number of continuouslyoverlapping values between the first sensor data and the signature dataof the signature file, determining, for each of the signature files, afirst total number of values of the signature data of the signature filethat are within a predetermined threshold from the first sensor data,and determining, for each of the signature files, a first total numberof continuous values of the signature data of the signature file thatare within the predetermined threshold from the first sensor data.Similarly, second sensor data and third sensor data may also be comparedwith the signature data of the signature files. FIG. 23 illustrates acomparison between sensor data 2302 and signature data 2301 of asignature file. Although three sensor data are described above, itshould be understood that sensor data from only a single sensor may becompared to signature data to identify a type of a disturbance event ona physical transmission line. In FIG. 23, a total number of overlappingvalues between the sensor data 2302 and the signature data 2301 of thesignature file is 6 (e.g., in FIG. 23, points 1-4, 7, and 11 are thepoints that overlap), a total number of continuously overlapping valuesbetween the sensor data 2302 and the signature data 2301 of thesignature file is 4 (e.g., points 1-4 in FIG. 23), a total number ofvalues of the signature data 2301 of the signature file that are withina predetermined threshold from the sensor data 2302 is 9 (e.g., points1-8 and 11 in FIG. 23), and a total number of continuous values of thesignature data 2301 of the signature file that are within thepredetermined threshold from the sensor data 2302 is 3 (e.g., points 5,6, and 8 in FIG. 23. FIG. 24, for example, illustrates a table 2402(this information along with table 2401 may be stored in the signaturedatabase 1534) that includes a total number of overlapping valuesbetween the sensor data and the signature data, a total number ofcontinuously overlapping values between the first sensor data and thesignature data of the signature file, a total number of values of thesignature data of the signature file that are within a predeterminedthreshold from the sensor data, and a total number of continuous valuesof the signature data of the signature file that are within thepredetermined threshold from the sensor data based on a comparison ofthe sensor data with signature data of the signature file. Althoughcomparisons between sensor data and signature data are discussed above,it should be understood that similar comparisons can be made betweenfirst sensor data from a first sensor and second sensor data from asecond sensor to determine a total number of overlapping values betweenthe first sensor data and the second sensor data, a total number ofcontinuously overlapping values between the first sensor data and thesecond sensor data, a total number of values of the second sensor datathat are within a predetermined threshold from the first sensor data,and a total number of continuous values of the second sensor data thatare within the predetermined threshold from the first sensor data basedon a comparison of the first sensor data with second sensor data. Basedon such a comparison between the first sensor data and the second sensordata, the server 1502 may determine whether the first sensor data andthe second sensor data correspond to a single disturbance event ormultiple different disturbance events.

The server 1502 may determine a first confidence value for eachsignature file based on a first total number of overlapping valuesbetween the first sensor data and the signature data, a first totalnumber of continuously overlapping values between the first sensor dataand the signature data of the signature file, a first total number ofvalues of the signature data of the signature file that are within apredetermined threshold from the first sensor data, and a first totalnumber of continuous values of the signature data of the signature filethat are within the predetermined threshold from the first sensor data.Similarly, server 1502 may determine a second confidence value and athird confidence value for each signature file based on a comparison ofthe second sensor data and the third sensor data with the signature dataof each signature file. FIG. 24 illustrates information regarding thesignature files (e.g., signature 1, signature 2, signature 3, andsignature 4) in table 2401 and comparisons of different sensor data withthe signature files in table 2402. The data in tables 2401 and 2402 maybe stored in the signature database 1534. As an example, table 2402 inFIG. 24 illustrates a confidence value for each signature file based ona comparison of sensor data with signature data of the signature file.These confidence values may be compared to a predetermined threshold toidentify a type of disturbance event on the physical transmission line.For example, FIG. 24 illustrates that a comparison of sensor data withsignature date of the signature file 2 results in a determination of aconfidence value of 73%. If this confidence value is greater than apredetermined threshold, a type of disturbance event associated with thesignature file 2 is identified. For example, signature database 1534 mayinclude information indicating that signature file 2 is associated witha hammer tap. Accordingly, when the confidence value for signature file2 exceeds a predetermined confidence threshold based on a comparison ofsensor data with the signature data of the signature file 2, the hammertap is identified as a type of disturbance event on the physicaltransmission line. The server 1502 (e.g., the disturbance identifyingsubsystem 1512) may identify one or more signature files whoseconfidence value exceeds a predetermined confidence threshold, andidentify a type of the disturbance event on the physical transmissionline based on the identified one or more signature files. The identifiedtype of disturbance event may be presented to a user via a userinterface (see presentation subsystem 1516 and client device 1504 inFIG. 15). Alternatively, the server 1502 (e.g., the disturbanceidentifying subsystem 1512) may identify the disturbance event as anunknown event on the physical transmission line when the confidencevalue for each of the signature files does not exceed a predeterminedconfidence threshold. A notification that the disturbance event is anunknown event may also be presented to a user via a user interface (seepresentation subsystem 1516 and client device 1504 in FIG. 15).

Once the type of disturbance event (e.g., a hammer tap) is presented tothe user, the server 1502 may request a user to confirm the accuracy ofthe identified type of disturbance event (see 2101 and 2102 in FIG. 21).For example, a user may be requested to confirm that the disturbanceevent is a hammer tap via a user interface (see 2101 and 2102 in FIG.21). When the user confirms the accuracy of the type of disturbanceevent presented to the user, the server 1502 may retrieve, from thesignature database 1534, one or more signature files. These retrievedone or more signature files may correspond to signature files that wereidentified to have a confidence value exceeding a predeterminedconfidence threshold and that were used to identify the type ofdisturbance event on the physical transmission line. For example, ifsignature file 2 from FIG. 24 was identified to have a confidence valuethat exceeds a predetermined confidence threshold, and the hammer tapwas identified as the type of disturbance event on the physicaltransmission line based on signature file 2, then signature file 2 isretrieved from the signature database 1534 when the user confirms theaccuracy of the type of disturbance event (e.g., hammer tap) presentedto the user. Once the signature files are retrieved from the signaturedatabase 1534 via communication subsystem 1514, the server 1502 (e.g.,the updating subsystem 1518) may compare the sensor data with thesignature data of the retrieved one or more signature files to determinedifferences between the sensor data and the signature data of theretrieved one or more signature files and may update the signature dataof the retrieved one or more signature files based on the determineddifferences. The updated signature files may be stored in the signaturedatabase 1534. It should be understood that multiple sensor data may becompared with the signature data of the retrieved signature files todetermine differences between multiple sensor data and the signaturedata of the retrieved signatures files, and the signature data of thesignature files may be updated based on such determined differences.Such update of the signature files may help refine accuracy of futuredetection of disturbance events.

In some embodiments, a neural network or other machine learning modelmay be trained and utilized to predict a location of a disturbance eventon the physical transmission line and a type of the disturbance event onthe physical transmission line. As an example, neural networks may bebased on a large collection of neural units (or artificial neurons).Neural networks may loosely mimic the manner in which a biological brainworks (e.g., via large clusters of biological neurons connected byaxons). Each neural unit of a neural network may be connected with manyother neural units of the neural network. Such connections can beenforcing or inhibitory in their effect on the activation state ofconnected neural units. In some embodiments, each individual neural unitmay have a summation function that combines the values of all its inputstogether. In some embodiments, each connection (or the neural unititself) may have a threshold function such that the signal must surpassthe threshold before it is allowed to propagate to other neural units.These neural network systems may be self-learning and trained, ratherthan explicitly programmed, and can perform significantly better incertain areas of problem solving, as compared to traditional computerprograms. In some embodiments, neural networks may include multiplelayers (e.g., where a signal path traverses from front layers to backlayers). In some embodiments, back propagation techniques may beutilized by the neural networks, where forward stimulation is used toreset weights on the “front” neural units. In some embodiments,stimulation and inhibition for neural networks may be more free-flowing,with connections interacting in a more chaotic and complex fashion.

Alternatively, the disturbance event may be identified as an unknownevent on the physical transmission line when the confidence value foreach of the signature files in the signature database 1534 does notexceed a predetermined confidence threshold. When the disturbance eventis identified as an unknown event, the disturbance event may bepresented to a user via a user interface as an unknown event (seepresentation subsystem 1516 and client device 1504). Further, the usermay be prompted to provide additional information about the disturbanceevent via the user interface so that the server 1502 can classify futuredisturbance events. For example, if the disturbance event is identifiedas an unknown event, then the user may be requested to identify thedisturbance event and provide additional information regarding thedisturbance event. In response to the user providing informationregarding the disturbance event, the server 1502 (e.g., updatingsubsystem 1518) may generate one or more new signature files includingnew signature data. The new signature files may be generated based onone or more sensor data (e.g., for which an unknown event wasidentified) and the information provided by the user of the disturbanceevent. Such generation of the new signature files may help identifyfuture detection of disturbance events.

The system 1500 may also distinguish voice patterns and identify humanpresence in specific areas that surround the physical transmission linebased on the above description. In other words, system 1500 maydistinguish between ambient environmental conditions, object interaction(e.g., a hammer tap) and minute optical, electrical, and wavedistortions created by human voice.

When a type of a disturbance event on the physical transmission line isidentified by the server 1502, the server 1502 (e.g., communicationsubsystem 1514) may communicate a signal to the physical transmissionline based on the type of the identified type of disturbance event. Forexample, when a disturbance event is identified as a hammer tap, theserver 1502 may communicate a signal to the physical transmission lineto disable (or cause shut down of) a portion of the physicaltransmission line that includes the disturbance event and re-route theinformation transmitted via the physical transmission line such that theportion of the physical transmission line that includes the disturbanceevent does not transmit the information. It should be understood thatonly a specific portion of the physical transmission line (e.g., theportion corresponding to the identified location of the disturbanceevent) may be disabled, while other portions of the physicaltransmission line may be allowed to function normally (e.g., otherportions of the physical transmission line where no disturbance eventhas been identified). Further, when a disturbance event is identified asa human voice, the sever 1502 may not communicate a signal to thephysical transmission line to disable a portion of the physicaltransmission line that detected the human voice and to re-routeinformation transmitted via the physical transmission line.

FIG. 25 illustrates a flowchart 2500 describing a method for identifyinga location of a disturbance event on a physical transmission line, inaccordance with one or more embodiments. The processing operations ofthe method presented below are intended to be illustrative andnon-limiting. In some embodiments, for example, the method may beaccomplished with one or more additional operations not described,and/or without one or more of the operations discussed. Additionally,the order in which the processing operations of the method areillustrated (and described below) is not intended to be limiting.

In some embodiments, the method may be implemented in one or moreprocessing devices (e.g., a digital processor, an analog processor, adigital circuit designed to process information, an analog circuitdesigned to process information, a state machine, and/or othermechanisms for electronically processing information). The processingdevices may include one or more devices executing some or all of theoperations of the method in response to instructions storedelectronically on an electronic storage medium. The processing devicesmay include one or more devices configured through hardware, firmware,and/or software to be specifically designed for execution of one or moreof the operations of the method.

In steps 2502 and 2504, first and second sensor data may be obtainedfrom first and second sensors, respectively, located on a physicaltransmission line. The first and second sensors may be optical sensors,electrical sensors, acoustical sensors, and/or fiber bragg grating (FBG)sensors and may be placed at different locations of the physicaltransmission line. The first and second sensor data received from thefirst and second sensors may include first and second measured values,respectively, of one or more disturbance events over a length of time.In some embodiments, the sensors may be located at predeterminedpositions on the physical transmission line and the informationregarding the location of the sensors on the physical transmission linemay be retrieved from a sensor database. In steps 2502 and 2504, whenthe first and second sensors measure a disturbance event (e.g., based ona detected disturbance event), first and second sensor data thatincludes first and second measured values, respectively, of thedisturbance event over a length of time may be obtained. The first andsecond measured values may be measured in gain or loss in optical power,acoustical power, and/or electrical resistance. The first and secondsensors may detect a single disturbance event or may detect multipledifferent disturbance events. Accordingly, the first sensor data and thesecond sensor data may correspond to a single disturbance event ormultiple different disturbance events.

In steps 2506, a first initial detection time of the first measuredvalues and a second initial detection time of the second measured valuesmay be determined and in step 2508, a time difference between the firstinitial detection time and the second initial detection time may bedetermined.

Further, in step 2510, a first distance of the disturbance event fromthe first sensor may be approximated based on the time difference and aknown constant (e.g., speed of sound and/or speed of light) and a seconddistance of the disturbance event from the second sensor may beapproximated based on the time difference and the known constant. Instep 2512, location of the disturbance event on the physicaltransmission line may be identified based on the approximated first andsecond distances of the disturbance event from the first sensor and thesecond sensor, respectively. In addition, the location of thedisturbance event on the physical transmission line may be identifiedfurther based on locations of these sensors on the physical transmissionline. For example, the information regarding the location of the sensorsmay be retrieved from the sensor database and this information may beutilized to identify the location of the disturbance event on thephysical transmission line. Additionally, the information regarding thedistance between the sensors may be retrieved from the sensor database1536 and this information may be utilized to identify the location ofthe disturbance event on the physical transmission line.

FIG. 26 illustrates a flowchart 2600 describing another method foridentifying a location of a disturbance event on a physical transmissionline, in accordance with one or more embodiments. In step 2602, sensingdata may be obtained from a sensing device located on a physicaltransmission line. The sensing data may include information regarding aproperty of a light beam emitted by the sensing device and reflectedback to the sensing device by one of the sensors and informationregarding timestamp values of the light beam emitted by the sensingdevice and reflected back to the sensing device by the one of thesensors. In step 2604, based on the sensing data, a roundtrip time ofthe light beam emitted by the sensing device and reflected back to thesensing device by the one of the sensors may be determined. Further, instep 2604, based on the sensing data, a change in the property of thelight beam emitted by the sensing device and reflected back to thesensing device by the one of the sensors may be determined. In step2606, based on the sensing data, a location of the disturbance event onthe physical transmission line may be identified. In other words, alocation of the disturbance event on the physical transmission line maybe identified based on (i) the roundtrip time of the light beam emittedby the sensing device and reflected back to the sensing device by theone of the sensors and (ii) the change in the property of the light beamemitted by the sensing device and reflected back to the sensing deviceby the one of the sensors. Additionally, information regarding thelocation of the sensing device may be retrieved from a sensor databaseand this information may be utilized to identify the location of thedisturbance event on the physical transmission line. Also, more than onesensing device may be placed at different locations of the physicaltransmission line to gather sensing data. Known distances between thesensors and the sensing device(s), a known constant (e.g., speed oflight and/or sound), and time resolution capabilities of the sensingdevice(s) can be taken into account to identify the location of thedisturbance event on the physical transmission line.

FIG. 27 illustrates a flowchart 2700 describing another method foridentifying a location of a disturbance event on a physical transmissionline, in accordance with one or more embodiments. In step 2702, sensingdata may be obtained from a sensing device located on a physicaltransmission line. The sensing data may include information regarding aproperty of a light beam emitted by the sensing device and reflectedback to the sensing device by one of the sensors and informationregarding timestamp values of another light beam emitted by the sensingdevice and reflected back to the sensing device by another one of thesensors. In step 2704, based on the sensing data, a change in theproperty of the light beam emitted by the sensing device and reflectedback to the sensing device by the one of the sensors may be determined.Further, in step 2704, based on the sensing data, a roundtrip time ofthe other light beam emitted by the sensing device and reflected back tothe sensing device by the other one of the sensors may be determined. Instep 2706, based on the sensing data, a location of the disturbanceevent on the physical transmission line may be identified. In otherwords, a location of the disturbance event on the physical transmissionline may be identified based on (i) the change in the property of thelight beam emitted by the sensing device and reflected back to thesensing device by the one of the sensors and (ii) the roundtrip time ofthe other light beam emitted by the sensing device and reflected back tothe sensing device by the other one of the sensors. Additionally,information regarding the location of the sensing device may beretrieved from a sensor database and this information may be utilized toidentify the location of the disturbance event on the physicaltransmission line. Also, more than one sensing device may be placed atdifferent locations of the physical transmission line to gather sensingdata. Known distances between the sensors and the sensing device(s), aknown constant (e.g., speed of light and/or sound), and time resolutioncapabilities of the sensing device(s) can be taken into account toidentify the location of the disturbance event on the physicaltransmission line.

FIG. 28 illustrates a flowchart 2800 describing a method for identifyinga type of a disturbance event on a physical transmission line, inaccordance with one or more embodiments. In step 2802, signature filescorresponding to previous disturbance events may be obtained. Each ofthe signature files may include signature data including previouslymeasured values of the previous disturbance events over a length oftime. The signatures files may be stored in a signature database and maybe retrieved from the signature database. In step 2804, the first andsecond sensor data (e.g., obtained from first sensor and second sensorlocated on the physical transmission line) may be compared with thesignature data of the signature files. The first and second sensor datamay be compared with the signature data of the signature files when atleast a portion of the first and second measured values (of the firstsensor data and the second sensor data) exceeds a predeterminedthreshold. Comparing the first and second sensor data with the signaturedata of the signature files may include determining, for each of thesignature files, a first total number of overlapping values between thefirst sensor data and the signature data of the signature file,determining, for each of the signature files, a second total number ofoverlapping values between the second sensor data and the signature dataof the signature file, determining, for each of the signature files, afirst total number of continuously overlapping values between the firstsensor data and the signature data of the signature file, determining,for each of the signature files, a second total number of continuouslyoverlapping values between the second sensor data and the signature dataof the signature file, determining, for each of the signature files, afirst total number of values of the signature data of the signature filethat are within a predetermined threshold from the first sensor data,determining, for each of the signature files, a second total number ofvalues of the signature data of the signature file that are within apredetermined threshold from the second sensor data, determining, foreach of the signature files, a first total number of continuous valuesof the signature data of the signature file that are within thepredetermined threshold from the first sensor data, and determining, foreach of the signature files, a second total number of continuous valuesof the signature data of the signature file that are within thepredetermined threshold from the second sensor data.

In step 2806, a first confidence value and a second confidence value foreach of the signature files may be determined based on the comparison ofthe first and second sensor data with the signature data of thesignature files. In step 2808, a determination is made as to whether thefirst confidence value or the second confidence value for a signaturefile exceeds a predetermined confidence threshold. If the answer is YES,in step 2810, one or more signature files whose confidence value exceedsa predetermined confidence threshold is identified. Further, in step2812, a type of disturbance event on the physical transmission line isidentified based on the identified one or more signature files. Forexample, a hammer tap may be identified as a type of disturbance eventon the physical transmission line.

In step 2814, the identified type of disturbance event may be presented,via a user interface, to a user and the user may be requested, via theuser interface, to confirm the accuracy of the identified type ofdisturbance event. For example, a user may be requested to confirm thatthe type of disturbance event is a hammer tap via a user interface. Instep 2816, when the user confirms the accuracy of the type ofdisturbance event presented to the user, one or more signature files maybe retrieve from a signature database. These retrieved one or moresignature files correspond to signature files that were identified tohave a confidence value exceeding a predetermined confidence thresholdand that were used to identify the type of disturbance event on thephysical transmission line.

In step 2818, the first and second sensor data (e.g., obtained fromfirst sensor and second sensor located on the physical transmissionline) may be compared with the signature data of the retrieved one ormore signature files to determine differences between the first sensordata and the signature data of the retrieved one or more signature filesand between the second sensor data and the signature data of theretrieved one or more signature files. In step 2820, the signature dataof the retrieved one or more signature files may be updated based on thedetermined differences. The updated one or more signature files may bestored in the signature database. Such update of the signature files mayhelp refine accuracy of future detection of disturbance events.

However, in step 2808, if the first confidence value or the secondconfidence value for a signature file does not exceed a predeterminedconfidence threshold (e.g., NO in step 2808), then we proceed to step2822. In step 2822, the disturbance event on the physical transmissionline is identified as an unknown event when the first confidence valueand the second confidence value for each of the signature files does notexceed the predetermined confidence threshold. Further, in step 2824,the disturbance event may be presented to a user via a user interface asan unknown event and the user, via the user interface, may be requestedto provide information about the unknown event. For example, the usermay be requested to provide a brief description of the disturbanceevent. In step 2826, one or more new signature files may be generatedbased on the first sensor data, the second sensor data, and theinformation provided by the user about the unknown event. Althoughflowchart 2800 describes a method for identifying a type of adisturbance event on a physical transmission line based on first andsecond sensor data, it should be understood that only one of the firstsensor data or the second sensor data may be used to identify a type ofa disturbance event on a physical transmission line.

In some embodiments, one or more components described herein may beconfigured in accordance with one or more variables, functions, or othercode represented by the following pseudocode:

// Variables _DeviceOutputFrequency = 5000 // number of data points persecond _DistanceTimingValue = 0 _CompleteTimeCycle = 0_StartingTimeStampValue = 0 _CenterDistance = 0 _SpeedOfWave = 0_MatchVariance = .15 _WavelengthVariance = .15 _DBVariance = 1_BaselineWavelength = 1450 _BaselineDB = −14_CompareResultThresholdCEPoM = .10 _CompareResultThresholdTEPoM = .05_CompareResultThresholdCPoVM = .10 _CompareResultThresholdTPoVM = .40Structure DisturbanceResult     DisturbanceStart = 0     DisturbanceEnd= 0     DisturbanceLength = 0 End Structure Structure CompareResults    ContExactPointsofMatch = 0     TotalExactPointsofMatch = 0    TotalContinousPointsofVariableMatch = 0    TotalPointsofVariableMatch = 0 End Structure Start Function Main    // Sensor Data Time of Flight for Two Sensors     IfCalibrateTimeOfFlight( ) = True Then     // Calibration Completed, andfuture disturbances can be determined by the following    EstimatedDisturbanceLocation =ReturnDistance(SensorDisturbance1.DisturbanceStart,SensorDisturbance2.DisturbanceStart)     End If     // Device TimingMethods     If CalibrateTimingValue( ) = True Then     // CalibrationCompleted, and future disturbances can be determined by the following    EstimatedDisturbanceLocationByTime(SensorDisturbance1.DisturbanceTimeStamp)    End If End Function Start Function GridMatch(LeftGridArray[ ],RightGridArray[ ], PointVarianceThreshold) Returns CompareResults Object    For r = 0 to RightGridArray.Count       If LeftGridArray[r] =RightGridArray[r] then          TotalExactPointsofMatch =TotalExactPointsofMatch + 1       End If       Check Value =(LeftGridArray[r] − RightGridArray[r])       If CheckValue <=PointVarianceThreshold then          TotalPointsofVariableMatch =TotalPointsofVariableMatch + 1       End If     Loop    Temp_ContExactPointsofMatch = 0 For r = 0 to RightGridArray.Count    For 1 = 0 to LeftGridArray.Count       If LeftGridArray[1] =RightGridArray[r] then          Temp_ContExactPointsofMatch =Temp_ContExactPointsofMatch + 1       Else          IfTemp_ContExactPointsofMatch > ContExactPointsofMatch            ContExactPointsofMatch = Temp_ContExactPointsofMatch         End If          Temp_ContExactPointsofMatch = 0       End If      Loop       If Temp_ContExactPointsofMatch > ContExactPointsofMatch               ContExactPointsofMatch = Temp_ContExactPointsofMatch      End If Loop Temp_ TotalContinousPointsofVariableMatch = 0 For r =0 to RightGridArray.Count     For 1 = 0 to LeftGridArray.Count      CheckValue = (LeftGridArray[1] − RightGridArray[r])       IfCheckValue <= PointVarianceThreshold then          Temp_TotalContinousPointsofVariableMatch = Temp_(—)TotalContinousPointsofVariableMatch + 1       Else          If Temp_TotalContinousPointsofVariableMatch >TotalContinousPointsofVariableMatch Then            TotalContinousPointsofVariableMatch = Temp_(—)TotalContinousPointsofVariableMatch End If          Temp_TotalContinousPointsofVariableMatch = 0       End If       Loop     IfTemp_ TotalContinousPointsofVariableMatch >TotalContinousPointsofVariableMatch Then      TotalContinousPointsofVariableMatch = Temp_(—)TotalContinousPointsofVariableMatch End If Loop     // Set values ofreturn object     CompareResults.ContExactPointsofMatch =ContExactPointsofMatch     CompareResults.TotalExactPointsofMatch =TotalExactPointsofMatch    CompareResults.TotalContinousPointsofVariableMatch =TotalContinousPointsofVariableMatch    CompareResults.TotalPointsofVariableMatch =TotalPointsofVariableMatch     Return CompareResults End Function StartFunction DetermineDisturbance (AnalysisBuffer[ ]) ReturnsDisturbanceResult     // This function determines disturbance based onmultiple factors // This example utilizes only wavelength and powervariance, however, multiple reading types based on device can beutilized     DisturbanceStart = 0     DisturbanceStarted = FalseDisturbanceEnd = 0     For b = 0 to AnalysisBuffer.Count       If((AnalysisBuffer[b].Wavelength − _BaselineWavelength) >_WavelengthVariance) OR ((AnalysisBuffer[b].DB − _BaselineDB) >_DBVariance) Then          If DisturbanceStarted = False then            DisturbanceStart = b             DisturbanceStarted = True         End If       Else          If DisturbanceStarted = True Then            DisturbanceEnd = b             Exit Loop          End If      End If     Loop DisturbanceResult.DisturbanceStart =DisturbanceStart DisturbanceResult.DisturbanceEnd = DisturbanceEnd    DisturbanceResult.DisturbanceLength = DisturbanceEnd −DisturbanceStart     Return DisturbanceResult End Function StartFunction ReturnDistance(TimeValue1, TimeValue2) Returns NumberDistancePer = _SpeedOfWave / _DeviceOutputFrequency DistanceDifference =TimeValue2− TimeValue1 SideDistance = DistanceDifference * DistancePerReturn (_CenterDistance + SideDistance) End Function Start FunctionCalculateSpeedofWave(TimeDifference, TotalLength,KnownDisturbanceDistance) as Number     CenterDistance = TotalLength / 2_CenterDistance = CenterDistance     CenterDifference =DisturbanceDistance − CenterDistance For t = 40 to 13000     If ((t /_DeviceOutputFrequency) * TimeDifference) = CenterDifference Then      Return t       Exit Loop     End If Next End Function //Calibration of Sensor Data Start Function CalibrateTimeOfFlight( )Returns Boolean *Read Device Information     *PopulateSensor1ReadBuffer[ ] with Device Information (Wavelength, Amplitude,etc) *Populate Sensor2ReadBuffer[ ] with Device Information (Wavelength,Amplitude, etc)     EstimatedDistance = Prompt User for EstimatedDistance of Disturbance     TotalKnownDistance = Prompt User for KnownDistance of Section     // Method One: Sensor Data Time of Flight forTwo Sensors     Sensor1DisturbanceResult =DetermineDisturbance(Sensor1ReadBuffer[ ]) Sensor2DisturbanceResult =DetermineDisturbance(Sensor2ReadBuffer[ ])     // Verify thatdisturbance is the same     SensorDisturbance1 =CopyFromArray(Sensor1ReadBuffer[ ],Sensor1DisturbanceResult.DisturbanceStart,Sensor1DisturbanceResult.DisturbanceLength)     SensorDisturbance2 =CopyFromArray(Sensor2ReadBuffer[ ],Sensor2DisturbanceResult.DisturbanceStart,Sensor2DisturbanceResult.DisturbanceLength)     SensorCompareResults =GridMatch(SensorDisturbance1[ ], SensorDisturbance2[ ], _MatchVariance)    If ((SensorCompareResults.ContExactPointsofMatch /SensorDisturbance1.Count) >= _CompareResultThresholdCEPoM) OR(SensorCompareResults.TotalExactPointsofMatch /SensorDisturbance1.Count) >= _CompareResultThresholdTEPoM) OR(SensorCompareResults.TotalContinousPointsofVariableMatch /SensorDisturbance1.Count) >= _CompareResultThresholdCPoVM) OR(SensorCompareResults.TotalPointsofVariableMatch /SensorDisturbance1.Count) >= _CompareResultThresholdTPoVM) Then     //Determine the speed of wave through the material     _ SpeedOfWave =CalculateSpeedofWave( (SensorDisturbance2.DisturbanceStart −SensorDisturbance1.DisturbanceStart) , TotalKnownDistance,EstimatedDistance)       Return True     Else       Return False End IfEnd Function Start Function CalculateTimingSpeed(DisturbanceTime1,DisturbanceTime2, TotalKnownDistance)     DisturbanceTimeDiff =DisturbanceTime2 − DisturbanceTime1     DisturbanceDistanceDiff =DisturbanceDistance2 − DisturbanceDistance1     DistancePerTime =DisturbanceDistanceDiff / DisturbanceTimeDiff     _DistanceTimingValue =DistancePerTime End Function // Starlight Start FunctionCalibrateTimingValue( ) Returns Boolean     // Method Two & Three:Timestamp Distance Calculation     TotalKnownDistance = Prompt User forKnown Distance of Section     *Prompt User to Create Disturbance at theBeginning of the Section     KnownDistance1 = Prompt User for KnownDistance of Section Disturbance *Read Device Information     *PopulateSensor1ReadBuffer[ ] with Device Information (Wavelength, Amplitude,etc) and Timestamp Information     SensorBeginDisturbanceResult =DetermineDisturbance(Sensor1ReadBuffer[ ])     *Set KnownKnowDistance1TimeStamp fromSensorBeginDisturbanceResult.DisturbanceStart     *Prompt User to CreateDisturbance at the End of the Section     KnownDistance2 = Prompt Userfor Known Distance of Section Disturbance *Read Device Information    *Populate Sensor1ReadBuffer[ ] with Device Information (Wavelength,Amplitude, etc) and Timestamp Information     SensorEndDisturbanceResult= DetermineDisturbance(Sensor1ReadBuffer[ ])    CalculateTimingSpeed(KnowDistance1TimeStamp, KnowDistance2TimeStamp,TotalKnownDistance) _CompleteTimeCycle = TotalKnownDistance *_DistanceTimingValue _StartingTimeStamp Value = KnowDistance1TimeStamp −(KnownDistance1 * _DistanceTimingValue)     Return True End FunctionStart Function EstimatedDisturbanceLocationByTime(DisturbanceTimeStamp)Returns Number     TickDisturbanceDiff = DisturbanceTimeStamp −_StartingTimeStampValue     CompletedCycles =Math.RoundDown(TickDisturbanceDiff/ _CompleteTimeCycle)     Return(TickDisturbanceDiff − (_CompleteTimeCycle * CompletedCycles)) *DistanceTimingValue End Function

Cable Assembly

FIGS. 29A and 29B show a cable assembly that illuminates using, forexample, light emitting diodes (LEDs) (see also visual indication 1528in FIG. 15) to provide an inspection personnel with real-timeinformation regarding the state of the cable assembly. The inner andouter jackets (or sheaths) of the cable assembly may be utilized for newor existing optical fiber cable designs as well as armored optic fiberassemblies that utilize metal or non-metallic tubing (spiral,inter-locking, or non-interlocking) with aramid and/or otherstrengthening materials.

FIGS. 29A and 29B show a cable assembly 2900 that includes an outerjacket 2901 (or outer sheath), a printed circuit board (PCB) 2902(including a plurality of LEDs 2905), an optional inner jacket 2903 (orinner sheath), and a core 2904 (e.g., a fiber optic cable or opticalfiber assembly which comprises at least one optical fiber enclosed in atubular member). The PCB 2902 may include circuitry to communicate withthe server 1502 to receive instructions to turn on/off one or more LEDs2905 and may include control circuitry to turn on/off the LEDs 2905based on such instructions. The outer jacket 2901 may have an innerdiameter than is slightly larger than an outer diameter of the core2904. The outer jacket 2901 may be composed of Polyvinly Chloride (PVC),Low smoke Zero Halogen (LSZH), Thermoplastic polyurethane (TPU),Ethylene Tetrafluoroethylene (ETFE), Optical Fiber Nonconductive Plenum(OFNP), or other types of plastic or rubber compounds. The outer jacket2901 may or may not be flame retardant and the outer jacket 2901 mayeither be translucent in color or may be a colored jacket withtransitions of translucent material at the location of the LEDs 2905 toallow emitted light to pass through. The PCB 2902 may include LEDs 2905and additional circuitry for control. The thickness of the PCB 2902 mayrange from 0.50-2.50 mm, the width of the PCB 2902 may vary, but istypically between 6 and 12 mm, and the length of the PCB 2902 may beconsistent with the length of the cable assembly. An example of thecircuitry for the PCB 2902 is illustrated in FIG. 30. FIG. 30 shows anSMD5050 design for analog control of Red Green Blue (RGB) LEDs. Howeveralternate LED control circuits such as an LPD8806 can be utilized toprovide individually accessible RGB LED control. The PCB 2902 mayinclude connections at the beginning and/or end of the assembly forconnecting to an external power source and additional control circuitsfor signal processing. The relative thickness of the PCB 2902 allows forcontouring around the inner jacket 2903 and/or core 2904.

The inner jacket 2903 may have an inner diameter than is slightly largerthan the outer diameter of the core 2904. The inner jacket 2903 may becomposed of PVC, LSZH, TPU, ETFE, OFNP, or other types of plastic orrubber compounds that can be utilized to color the inner jacket 3 whenutilizing a translucent outer jacket 2901. The core 2904 (e.g., a fiberoptic cable or optical fiber assembly which may comprise at least oneoptical fiber enclosed in a tubular member) may be composed of PVC,High-density Polyethylene (HDPE) or Silicone. Optionally, the core 2904may be an armored assembly composed of a metallic or non-metallicspiral, inter-locking or non-interlocking tube. Core 2904 may includeoptional strengthening materials, such as aramid or glass fibers,plastic or metal wiring or similar strength and rigidity increasingmaterials.

The PCB 2902 can be integrated into the cable assembly 2900 usingmultiple methods based on the outer and inner jacket materials and theenvironmental and performance requirements of the cable assembly 2900.

FIG. 29A shows a cable assembly 2900 without channels (or channelopenings). In FIG. 29, the PCB 2902 (which includes a plurality of LEDs2905) is placed between the outer jacket 2901 and core 2904. Forexample, the PCB 2902 may be placed on top of the core 2904 using anadhesive to ensure proper alignment of the PCB 2902 with the overallcable assembly 2900. Alternatively, as illustrated in FIG. 29B, the PCB2902 may be placed between the inner jacket 2903 and outer jacket 2901.For example, the PCB 2902 may be placed on top of the inner jacket 2903using an adhesive to ensure proper alignment of the PCB 2902 with theoverall cable assembly 2900. FIG. 29B shows a YZ plane view of the cable2900 assembly illustrated in FIG. 29A.

The spacing between the outer jacket 2901 and the core 2904 (or betweenthe outer jacket 2901 and the inner jacket 2903) may be approximately0.50-2.50 mm depending upon the thicknesses of the PCB 2902 and thematerial of the outer jacket 2901. For example, a rigid PVC material forthe outer jacket 2901 may require spacing equivalent to the full PCBthickness, whereas a rubber or rubber type compound would allow inherentcontouring/molding around the PCB 2902. Utilizing no channels (orchannel openings) for the outer jacket 2901 may ensure that the inherentdurability of the outer jacket 2901 is unaffected.

The outer jacket 2901 may be translucent, thereby, allowing light fromthe LEDs 2905 to be seen. When a location of a disturbance event (e.g.,a location of an intrusion attempt) on the cable assembly 2900 isidentified, the system 1500 may be configured to supply a signal vianetwork 1550 to the cable assembly 2900 so that the LEDs 2905 that arelocated at or near the location of the disturbance event can beilluminated. Additionally, the system 1500 may be configured to supply asignal via network 1550 to the cable assembly 2900 so that the LEDs 2905can be illuminated to indicate a type of disturbance event. For example,different LEDs can be illuminated (different patterns) to identifydifferent types of disturbance events. Additionally, or alternatively,different colors can be illuminated to identify different types ofdisturbance events. Further, the LEDs can also be illuminated to showspecific status information such as warning conditions and maintenanceactivity. Although only one strip of LEDs 2905 is illustrated in FIGS.29A and 29B, it should be understood that a plurality of PCBs 2902 canbe included between the core 2904 and outer jacket 2901 (or between theinner jacket 2903 and the outer jacket 2901) such that the LEDs 2905 onthe PCB 2902 can be viewed from different angles and directions.

FIG. 31A shows a cable assembly 3100 that includes a core 3104, PCB 3102(including a plurality of LEDs 3105), and an outer jacket 3101. Theouter jacket 3101 includes a channel (or channel opening) 3106 thatallows the PCB 3102 to be positioned within the channel opening 3106.The channel may be molded, cut, or otherwise imparted on the inside ofthe outer jacket 3101. The PCB 3102 may include circuitry to communicatewith the server 1502 to receive instructions to turn on/off one or moreLEDs 3105 and may include control circuitry to turn on/off the LEDs 3105based on such instructions. FIG. 31B shows another view of the cableassembly 3100 (view of the YZ plane). In FIG. 31B, the outer jacket 3101is illustrated to include a plurality of channel openings 3106A-D(within which a plurality of PCBs 3102 may be positioned). Further, FIG.31B illustrates core 3104. Although the cable assembly 3100 does notillustrate an inner jacket, it should be understood that an inner jacketmay be included in the cable assembly 3100 such that the inner assemblysurrounds the core 3104 and the PCB 3102 may be positioned between theinner jacket and the outer jacket 3101.

FIG. 31B also illustrates an outer layer 3101A of the outer jacket 3101,a first inner layer 3101B of the outer jacket 3101, and a second innerlayer 3101C of the outer jacket 3101. Here, the first inner layer 3101Bcorresponds to a top portion of the channel 3106A. The first inner layer3101B is formed in a section of the outer jacket 3101 that includes thechannel opening 3106A and the second inner layer 3101C is formed in asection of the outer jacket 3101 that does not include the channelopening 3106A. The first thickness between the outer layer 3101A and thefirst inner layer 3101B is smaller than the second thickness between theouter layer 3101A and the second inner layer 3101C. The shape of thechannel opening 3106 can be rectangular, square, circular, trapezoidal,or any other shape that can allow the PCB 3102 to be positioned withinthe channel opening 3106.

FIG. 31C illustrates another view of the channel assembly 3100 (view ofthe YX plane). In FIG. 31C, a PCB 3102 is illustrated to be positionedwithin the channel opening 3106A and between the outer jacket 3101 andthe core 3104. Here, a depth of the channel opening is illustrated asbeing consistent throughout a length of the outer jacket in the Xdirection. This allows the PCB 3102 to stay in a specific orientationand position within the channel 3106A, while also allowing for removalof the PCB 3102 for activities such as repair, by allowing the PCB 3102to slide out of the channel 3106A when adhesives have not been utilizedduring the manufacturing process. The depth of the channel opening 3106Amay be measured based on a difference between the second thickness(e.g., the second thickness between the outer layer 3101A and the secondinner layer 3101C) and the first thickness (e.g., the first thicknessbetween the outer layer 3101A and the first inner layer 3101B).Alternatively, the depth of the channel opening 3106A may be measured asthe difference between the second thickness and the first thickness plusa spacing between the core 3104 and the second inner layer 3101C. Thespacing between the core 3104 and the second inner layer 3101C (e.g.,the spacing between the core 3104 and the outer jacket 3101) may be lessthan 1 mm. The channel opening 3106 may have a depth of approximately0.50-2.50 mm dependent on the type and size of the PCB 3102 that isembedded within the channel opening 3106.

FIG. 31D illustrates another view of the channel assembly 3100 (view ofthe YX plane) and is an alternate to the configuration described andillustrated with regard to FIG. 31C. For example, FIG. 31D illustrates amolded channel opening 3106A (that may contour around each PCB 3102component) such that a depth of the channel opening 3106A varies along alength of the outer jacket 3101. The depth of the channel opening 3106Amay vary by 1 mm because of the varied depth of the channel opening3106A. This varied depth allows strict control of the PCB 3102 and mayprevent removal or movement under normal and adverse operatingcircumstances. Adhesives between the core 3104 and the PCB 3102 may beutilized. However, an adhesive is not required.

FIG. 32A shows a cable assembly 3200 that includes a core 3204, PCB 3202(including a plurality of LEDs 3205), an outer jacket 3201, and an innerjacket 3203. The inner jacket 3203 includes a channel (or channelopening or depression) 3208 that allows the PCB 3202 to be positionedwithin the channel opening 3208. The channel may be molded, cut, orotherwise imparted on the outside of the inner jacket 3203. FIG. 32Bshows another view of the cable assembly 3200 (view of the YZ plane). InFIG. 32B, the inner jacket 3203 is illustrated to include a plurality ofchannel openings 3208A-D (within which a plurality of PCBs 3202 may bepositioned). Further, FIG. 32B also illustrates the outer jacket 3201and core 3204.

FIG. 32B also illustrates an inner layer 3203A of the inner jacket 3203,a first outer layer 3203B of the inner jacket 3203, and a second outerlayer 3203C of the inner jacket 3203. Here, the second inner layer 3203Ccorresponds to a bottom portion of the channel opening 3208A. The secondouter layer 3203C is formed in a section of the inner jacket 3203 thatincludes the channel opening 3208A and the first outer layer 3203B isformed in a section of the inner jacket 3203 that does not include thechannel opening 3208A. The first thickness between first outer layer3203B and the inner layer 3203A is larger than the second thicknessbetween the second outer layer 3203C and the inner layer 3203A. Theshape of the channel opening 3208 can be rectangular, square, circular,trapezoidal, or any other shape that can allow the PCB 3202 to bepositioned within the channel opening 3208.

A depth of the channel opening 3208 may be consistent throughout alength of the outer jacket 3201 in the X direction. The depth of thechannel opening 3208 may be measured based on a difference between thefirst thickness (e.g., the first thickness between first outer layer3203B and the inner layer 3203A) and the second thickness (e.g., thesecond thickness between the second outer layer 3203C and the innerlayer 3203A). Alternatively, the depth of the channel opening 3208A maybe measured as the difference between the first thickness and the secondthickness plus a spacing between the first outer layer 3203B and theouter jacket 3201. The spacing between the first outer layer 3203B andthe outer jacket 3201 (e.g., the spacing between the inner jacket 3203and the outer jacket 3201) may be less than 1 mm. The channel opening3208 may have a depth of approximately 0.50-2.50 mm dependent on thetype and size of the PCB 3202 that is embedded within the channelopening 3208.

The channel opening 3208 may be included within the inner jacket 3203 insituations where the durability, rigidity or performance of the materialof the outer jacket 3201 could be negatively affected by the varyingdiameter/thickness of the channel within the outer jacket 3201. Such aconfiguration in FIGS. 32A and 32B may ensure that environmentaldurability, bending radius, and other stress factors do not affect theintegrity of the outer jacket 3201.

The channel opening 3208 within the inner jacket 3203 ensures that thePCB 3202 stays within a fixed position relative to the rest of the cableassembly 3200. This configuration in FIGS. 32A and 32B allows the PCB3202 to stay in a specific orientation and position, while allowing forremoval of the PCB 3202 for activities such as repair, by allowing thePCB 3202 to slide out of the channel 3208 when adhesives have not beenused during the manufacturing process.

The LEDs described above may provide alarm response personnel withvisual indicators attached to transmission lines (or their enclosures)that provide specific status information such as warning conditions,maintenance activity, intrusion information, and/or locationinformation. The spacing between LEDs may be varied based on severalfactors. Some of the factors may include length, width, and/or diameterof the cable assembly. For example, a shorter cable assembly may haveless spacing between the LEDs compared to a longer cable.

Further, a number of LEDs that are lit may depend on a length of thedisturbance event on the physical transmission line. For example, if thedisturbance event spans a large portion of the transmission line, thenseveral LEDs (that span the portion of the physical transmission linethat has been disturbed) may be lit. Alternatively, only two LEDs may belit (e.g., an LED at a start location of the disturbance event on thephysical transmission line and at an end location of the disturbanceevent on the physical transmission line). Alternatively, only one LEDmay be lit that is closest to the identified location of the disturbanceevent on the physical transmission line. By lighting few number of LEDs,power can be saved. Long distances of continuously lit LEDs requirelarge amounts of power. For that reason, the number of LEDs that aresimultaneously lit may be limited to ensure that usage of power by theLEDs is below a predetermined threshold. The server 1502 may determine anumber of LEDs to be lit and/or the pattern of the LEDs to be lit basedon the length of the disturbance event on the physical transmission line(in other words, a length of the portion of the physical transmissionline that has been disturbed), amount of power supply required for eachof the LEDs, and/or color of the LEDs to be visually displayed so thatthe power used by the LEDs does not exceed a predetermined threshold.Alternatively, control circuitry of the PCB may determine a number ofLEDs to be lit and/or the pattern of the LEDs to be lit based on thelength of the disturbance event on the physical transmission line (inother words, a length of the portion of the physical transmission linethat has been disturbed), amount of power supply required for each ofthe LEDs, and/or color of the LEDs to be visually displayed so that thepower used by the LEDs does not exceed a predetermined threshold.

In addition to visually indicating that there is a disturbance event ata specific location of the physical transmission line, the LEDs may belit based on one or more patterns. For example, one LED may be made toblink (e.g., an LED closest to the identified location of thedisturbance event on the physical transmission line), thereby, providinga network personnel better visibility of the exact location of thedisturbance event on the physical transmission line. Alternatively, aseries of LEDs may be lit one after another (a “chase” effect) thatlocated between a start location of the disturbance event on thephysical transmission line and an end location of the disturbance eventon the physical transmission line. Such a chase effect may allow verylong sections of the physical transmission line to be illuminatedwithout exceeding a power level beyond a predetermined threshold.Further, different color LEDs may be lit to indicate differentinformation to a network personnel. For example, a red LED may indicatethat there is a disturbance event on the physical transmission line, agreen LED may indicate that there is no disturbance event on thephysical transmission line, and a blue LED may indicate that maintenanceis being conducted on the physical transmission line. It should beunderstood that these are merely some examples, and various combinationsof patterns and colors may be used to provide alarm response personnelwith specific status information such as warning conditions, maintenanceactivity, intrusion information, and/or location information.

FIG. 33 shows an architecture and operation of a visual indicationsystem 3300 in conjunction with a PDS manager architecture. One or morecomponents of the visual indication system 3300 illustrated in FIG. 33may correspond to one or more components of the system 1500 in FIG. 15.

FIG. 33 shows alarm monitoring devices 3307 that detect disturbances toa transmission line 3306. The transmission line 3306 may be affixed witha visual indication collar 3304, which includes a series of LED lightsmanaged and controlled by an electronic controller 3305. As the alarmmonitoring devices 3307 detect disturbances on the transmission line3306, data is sent to the PDS manager architecture (see 3301 and 3302 inFIG. 33) and this data is processed by the PDS manager system and stateinformation (such as “no issue,” “alarm,” “warning,” or “maintenance”conditions) may be produced.

The PDS Manager Web Server may provide real-time data feed in the formof a web service that the visual indicator system controller 3305 mayrequest via Ethernet, WiFi or other wireless radio communication (see3303 in FIG. 33). Sensor data status information may be processed by thevisual indicator system controller 3305 and based on user configurationwithin the controller, visual indicators (such as LED lights) maydisplay on the transmission line 3306. For example, “no issue”conditions may light the LEDs on the “visual indicator collar” as green,“warning” conditions as yellow, “maintenance” conditions in blue and“alarm” conditions in red. As the PDS Manager continues to updatetransmission line state information, the visual indication system 3300may update visual indicators in real-time so that response personnelknow current transmission line status.

The visual indication system 3300 can utilize multiple form factors,including a “visual indicator collar” as shown in FIG. 33, a visualindicator “strip” as shown in FIG. 34 which uses a series of connectedlights that affix to the transmission line or one or more indicators asa visual indicator “box” affixed to the transmission line. When thesystem 3400 is utilized with a “visual indicator strip” 3401, locationinformation provided by the PDS Manager is utilized by the visualindicator system controller 3404 to visually indicate the location ofthe disturbance (e.g., 3403 in FIG. 34 shows a series lights illuminatedafter a disturbance at location 3402 is detected). This providesresponse personnel the ability to pinpoint the exact location of adisturbance.

In some embodiments, the various computers and subsystems illustrated inFIG. 15 may include one or more computing devices that are programmed toperform the functions described herein. The computing devices mayinclude one or more electronic storages (e.g., database(s) 1532, whichmay include signature database 1534, sensor database 1536, etc., orother electric storages), one or more physical processors programmedwith one or more computer program instructions, and/or other components.The computing devices may include communication lines or ports to enablethe exchange of information with a network (e.g., network 1550) or othercomputing platforms via wired or wireless techniques (e.g., Ethernet,fiber optics, coaxial cable, WiFi, Bluetooth, near field communication,or other technologies). The computing devices may include a plurality ofhardware, software, and/or firmware components operating together. Forexample, the computing devices may be implemented by a cloud ofcomputing platforms operating together as the computing devices.

The electronic storages may include non-transitory storage media thatelectronically stores information. The electronic storage media of theelectronic storages may include one or both of (i) system storage thatis provided integrally (e.g., substantially non-removable) with serversor client devices or (ii) removable storage that is removablyconnectable to the servers or client devices via, for example, a port(e.g., a USB port, a firewire port, etc.) or a drive (e.g., a diskdrive, etc.). The electronic storages may include one or more ofoptically readable storage media (e.g., optical disks, etc.),magnetically readable storage media (e.g., magnetic tape, magnetic harddrive, floppy drive, etc.), electrical charge-based storage media (e.g.,EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.),and/or other electronically readable storage media. The electronicstorages may include one or more virtual storage resources (e.g., cloudstorage, a virtual private network, and/or other virtual storageresources). The electronic storage may store software algorithms,information determined by the processors, information obtained fromservers, information obtained from client devices, or other informationthat enables the functionality as described herein.

The processors may be programmed to provide information processingcapabilities in the computing devices. As such, the processors mayinclude one or more of a digital processor, an analog processor, adigital circuit designed to process information, an analog circuitdesigned to process information, a state machine, and/or othermechanisms for electronically processing information. In someembodiments, the processors may include a plurality of processing units.These processing units may be physically located within the same device,or the processors may represent processing functionality of a pluralityof devices operating in coordination. The processors may be programmedto execute computer program instructions to perform functions describedherein of subsystems 1512-1518 or other subsystems. The processors maybe programmed to execute computer program instructions by software;hardware; firmware; some combination of software, hardware, or firmware;and/or other mechanisms for configuring processing capabilities on theprocessors.

It should be appreciated that the description of the functionalityprovided by the different subsystems 1512-1518 described herein is forillustrative purposes, and is not intended to be limiting, as any ofsubsystems 1512-1518 may provide more or less functionality than isdescribed. For example, one or more of subsystems 1512-1518 may beeliminated, and some or all of its functionality may be provided byother ones of subsystems 1512-1518. As another example, additionalsubsystems may be programmed to perform some or all of the functionalityattributed herein to one of subsystems 1512-1518.

Although the present invention has been described in detail for thepurpose of illustration based on what is currently considered to be themost practical and preferred embodiments, it is to be understood thatsuch detail is solely for that purpose and that the invention is notlimited to the disclosed embodiments, but, on the contrary, is intendedto cover modifications and equivalent arrangements that are within thescope of the appended claims. For example, it is to be understood thatthe present invention contemplates that, to the extent possible, one ormore features of any embodiment may be combined with one or morefeatures of any other embodiment.

The present techniques will be better understood with reference to thefollowing enumerated embodiments:

A1. A method for identifying a location of a disturbance event on aphysical transmission line, the method comprising: obtaining, from afirst sensor among sensors on a physical transmission line, first sensordata, the first sensor data including first measured values of thedisturbance event over a length of time; obtaining, from a second sensoramong the sensors on the physical transmission line, second sensor data,the second sensor data including second measured values of thedisturbance event over the length of time; determining a first initialdetection time of the first measured values and a second initialdetection time of the second measured values; determining a timedifference between the first initial detection time and the secondinitial detection time; approximating a first distance of thedisturbance event from the first sensor based on the time difference anda known constant and a second distance of the disturbance event from thesecond sensor based on the time difference and the known constant; andidentifying a location of the disturbance event on the physicaltransmission line based on the approximated first and second distances.A2. The method of embodiment A1, wherein the location of the disturbanceevent on the physical transmission line is identified further based onlocations of the first and second sensors on the physical transmissionline.A3. The method of any of embodiments A1-2, further comprising:obtaining, from a sensing device located on the physical transmissionline, sensing data, the sensing data including information regardingtimestamp values of a light beam emitted by the sensing device andreflected back to the sensing device by one of the sensors andinformation regarding a property of the light beam emitted by thesensing device and reflected back to the sensing device by the one ofthe sensors; determining, based on the sensing data, (i) a roundtriptime of the light beam emitted by the sensing device and reflected backto the sensing device by the one of the sensors and (ii) a change in theproperty of the light beam emitted by the sensing device and reflectedback to the sensing device by the one of the sensors; and identifyingthe location of the disturbance event on the physical transmission linefurther based on (i) the roundtrip time of the light beam emitted by thesensing device and reflected back to the sensing device by the one ofthe sensors and (ii) the change in the property of the light beamemitted by the sensing device and reflected back to the sensing deviceby the one of the sensors.A4. The method of any of embodiments A1-3, wherein the location of thedisturbance event on the physical transmission line is identifiedfurther based on a location of the sensing device on the physicaltransmission line.A5. The method of any of embodiments A1-4, further comprising:obtaining, from a sensing device located on the physical transmissionline, sensing data, the sensing data including information regarding aproperty of a light beam emitted by the sensing device and reflectedback to the sensing device by one of the sensors and informationregarding timestamp values of another light beam emitted by the sensingdevice and reflected back to the sensing device by another one of thesensors; determining, based on the sensing data, (i) a change in theproperty of the light beam emitted by the sensing device and reflectedback to the sensing device by the one of the sensors and (ii) aroundtrip time of the other light beam emitted by the sensing device andreflected back to the sensing device by the other one of the sensors;and identifying the location of the disturbance event on the physicaltransmission line further based on (i) the change in the property of thelight beam emitted by the sensing device and reflected back to thesensing device by the one of the sensors and (ii) the roundtrip time ofthe other light beam emitted by the sensing device and reflected back tothe sensing device by the other one of the sensors.A6. The method of any of embodiments A1-5, wherein the known constant isat least one of speed of sound or speed of light.A7. The method of any of embodiments A1-6, further comprising:presenting, via a user interface, the location of the disturbance eventon the physical transmission line.A8. The method of any of embodiments A1-7, further comprising:determining whether the first measured values and the second measuredvalues correspond to a single disturbance event or multiple disturbanceevents based on (i) a comparison of time durations of the first andsecond measured values and (ii) a comparison of peak/valley magnitudesof the first and second measured values.A9. The method of any of embodiments A1-8, wherein the property of thelight beam includes at least one of wavelength or amplitude.A10. The method of any of embodiments A1-9, wherein the light beam isemitted by the sensing device via the physical transmission line andreflected back to the sensing device via the physical transmission line.A11. The method of any of embodiments A1-10, wherein the property of thelight beam includes at least one of wavelength or amplitude.A12. The method of any of embodiments A1-11, wherein the light beam isemitted by the sensing device via the physical transmission line andreflected back to the sensing device via the physical transmission line,and wherein the other light beam is emitted by the sensing device viathe physical transmission line and reflected back to the sensing devicevia the physical transmission line.A13. The method of any of embodiments A1-12, wherein the sensors includeoptical sensors, electrical sensors, acoustical sensors, or fiber bragggrating sensors.A14. The method of any of embodiments A1-13, further comprising:obtaining signature files corresponding to previous disturbance events,each of the signature files including signature data includingpreviously measured values of the previous disturbance events over thelength of time; comparing the first and second sensor data with thesignature data of the signature files; determining a first confidencevalue and a second confidence value for each of the signature filesbased on the comparison of the first and second sensor data with thesignature data of the signature files; identifying one or more signaturefiles whose said first confidence value or said second confidence valueexceeds a predetermined confidence threshold; and identifying a type ofthe disturbance event on the physical transmission line based on theidentified one or more signature files.A15. The method of any of embodiments A1-14, wherein comparing the firstand second sensor data with the signature data of the signature filescomprises: determining, for each of the signature files, a first totalnumber of overlapping values between the first sensor data and thesignature data of the signature file, determining, for each of thesignature files, a second total number of overlapping values between thesecond sensor data and the signature data of the signature file,determining, for each of the signature files, a first total number ofcontinuously overlapping values between the first sensor data and thesignature data of the signature file, and determining, for each of thesignature files, a second total number of continuously overlappingvalues between the second sensor data and the signature data of thesignature file, and wherein the first confidence value and the secondconfidence value for each of the signature files are based on the firstand second total number of overlapping values and the first and secondtotal number of continuously overlapping values.A16. The method of any of embodiments A1-15, wherein comparing the firstand second sensor data with the signature data of the signature filescomprises: determining, for each of the signature files, a first totalnumber of values of the signature data of the signature file that arewithin a predetermined threshold from the first sensor data,determining, for each of the signature files, a second total number ofvalues of the signature data of the signature file that are within apredetermined threshold from the second sensor data, determining, foreach of the signature files, a first total number of continuous valuesof the signature data of the signature file that are within thepredetermined threshold from the first sensor data, and determining, foreach of the signature files, a second total number of continuous valuesof the signature data of the signature file that are within thepredetermined threshold from the second sensor data, and wherein thefirst confidence value and the second confidence value for each of thesignature files are based on the first and second total number of valuesand the first and second total number of continuous values.A17. The method of any of embodiments A1-16, wherein the first andsecond sensor data are compared with the signature data of the signaturefiles when at least a portion of the first and second measured valuesexceeds a predetermined threshold.A18. The method of any of embodiments A1-17, further comprising:presenting, via a user interface, the identified type of the disturbanceevent; requesting, via the user interface, a user to confirm accuracy ofthe identified type of disturbance event; retrieving, from a memory, theone or more signature files when the user confirms the accuracy of theidentified type of the disturbance event; comparing the first and secondsensor data with the signature data of the one or more signature filesto determine differences between the first sensor data and the signaturedata of the one or more signature files and between the second sensordata and the signature data of the one or more signature files; andupdating the signature data of the one or more signature files based onthe determined differences.A19. The method of any of embodiments A1-18, further comprising:identifying the disturbance event on the physical transmission line asan unknown event when the first confidence value and the secondconfidence value for each of the signature files does not exceed thepredetermined confidence threshold; presenting, via a user interface,the disturbance event as the unknown event; requesting, via the userinterface, information about the unknown event; and generating one ormore new signature files based on the first sensor data, the secondsensor data, and the information about the unknown event.A20. The method of any of embodiments A1-19, further comprising:obtaining signature files corresponding to previous disturbance events,each of the signature files including signature data includingpreviously measured values of the previous disturbance events over thelength of time; comparing the first sensor data with the signature dataof the signature files; determining a first confidence value for each ofthe signature files based on the comparison of the first sensor datawith the signature data of the signature files; identifying one or moresignature files whose said first confidence value exceeds apredetermined confidence threshold; and identifying a type of thedisturbance event on the physical transmission line based on theidentified one or more signature files.A21. A method for identifying a location of a disturbance event on aphysical transmission line, the method comprising: obtaining, from asensing device located on the physical transmission line, sensing data,the sensing data including information regarding timestamp values of alight beam emitted by the sensing device and reflected back to thesensing device by a sensor located on the physical transmission line andinformation regarding a property of the light beam emitted by thesensing device and reflected back to the sensing device by the sensor;determining, based on the sensing data, (i) a roundtrip time of thelight beam emitted by the sensing device and reflected back to thesensing device by the sensor and (ii) a change in the property of thelight beam emitted by the sensing device and reflected back to thesensing device by the sensor; and identifying the location of thedisturbance event on the physical transmission line based on (i) theroundtrip time of the light beam emitted by the sensing device andreflected back to the sensing device by the sensor and (ii) the changein the property of the light beam emitted by the sensing device andreflected back to the sensing device by the sensor.A22. A system comprising: one or more processors; and memory storinginstructions that when executed by the processors cause the processorsto effectuate operations comprising those of any of embodiments A1-21.A23. A tangible, non-transitory, machine-readable medium storinginstructions that when executed by a data processing apparatus cause thedata processing apparatus to perform operations comprising those of anyof embodiments A1-21.B1. A cable assembly comprising: an outer jacket; a printed circuitboard including light emitting diodes; and a cable configured totransmit information, wherein the outer jacket includes a channelopening, and the printed circuit board is configured to be positionedwithin the channel opening and between the cable and the outer jacket.B2. The cable assembly of embodiment B1, further comprising: an innerjacket, wherein the inner jacket surrounds the cable and the outerjacket surrounds the inner jacket.B3. The cable assembly of any of embodiments B1-2, wherein a firstthickness between an outer layer and an inner layer of the outer jacketin a section of the outer jacket that includes the channel opening isless than a second thickness between the outer layer and the inner layerof the outer jacket in another section of the outer jacket that does notinclude the channel opening.B4. The cable assembly of any of embodiments B1-3, wherein a shape ofthe channel opening is rectangular, square, circular, or trapezoidal.B5. The cable assembly of any of embodiments B1-4, wherein the outerjacket includes a plurality of channel openings and wherein a pluralityof printed circuit boards are configured to be positioned within theplurality of channel openings between the cable and the outer jacket.B6. The cable assembly of any of embodiments B1-5, wherein a depth ofthe channel opening is consistent throughout a length of the outerjacket.B7. The cable assembly of any of embodiments B1-6, wherein a depth ofthe channel opening varies along a length of the outer jacket.B8. The cable assembly of any of embodiments B1-7, wherein the depth ofthe channel opening corresponds to a difference between a firstthickness and a second thickness between an outer layer and an innerlayer of the outer jacket, the first thickness is measured between theouter layer and the inner layer of the outer jacket in a section of theouter jacket that includes the channel opening, and the second thicknessis measured between the outer layer and the inner layer of the outerjacket in another section of the outer jacket that does not include thechannel opening.B9. The cable assembly of any of embodiments B1-8, wherein the printedcircuit board is configured to be positioned within the channel openingbetween the inner jacket and the outer jacket.B10. The cable assembly of any of embodiments B1-9, wherein the depth ofthe channel opening varies along the length of the outer jacket based ona size of the light emitting diodes.B11. The cable assembly of any of embodiments B1-10, wherein the outerjacket is translucent.B12. A cable assembly comprising: an inner jacket; an outer jacket; aprinted circuit board including light emitting diodes; and a cableconfigured to transmit information, wherein the inner jacket includes achannel opening, and the printed circuit board is configured to bepositioned within the channel opening and between the inner jacket andthe outer jacket.B13. The cable assembly of embodiment B12, wherein the inner jacketsurrounds the cable and the outer jacket surrounds the inner jacket.B14. The cable assembly of any of embodiments B12-13, wherein a firstthickness between an outer layer and an inner layer of the inner jacketin a section of the inner jacket that includes the channel opening isless than a second thickness between the outer layer and the inner layerof the inner jacket in another section of the inner jacket that does notinclude the channel opening.B15. The cable assembly of any of embodiments B12-14, wherein the innerjacket includes a plurality of channel openings and wherein a pluralityof printed circuit boards are configured to be positioned within theplurality of channel openings between the inner jacket and the outerjacket.B16. The cable assembly of any of embodiments B12-15, wherein a depth ofthe channel opening is consistent throughout a length of the outerjacket.B17. The cable assembly of any of embodiments B12-16, wherein the depthof the channel opening corresponds to a difference between a firstthickness and a second thickness between an outer layer and an innerlayer of the inner jacket, the first thickness is measured between theouter layer and the inner layer of the inner jacket in a section of theinner jacket that includes the channel opening, and the second thicknessis measured between the outer layer and the inner layer of the innerjacket in another section of the inner jacket that does not include thechannel opening.B18. The cable assembly of any of embodiments B12-17, wherein the outerjacket is translucent.B19. An outer jacket for a cable that transmits information, the outerjacket comprising: an outer layer; and an inner layer, wherein the innerlayer comprises a channel opening to allow a plurality of light emittingdiodes to be housed within the channel opening.B20. An inner jacket for a cable that transmits information, the innerjacket comprising: an inner layer; and an outer layer, wherein the outerlayer comprises a channel opening to allow a plurality of light emittingdiodes to be housed within the channel opening.

What is claimed is:
 1. A cable assembly comprising: an outer jacket; aprinted circuit board including light emitting diodes; and a cableconfigured to transmit information, wherein the outer jacket includes achannel opening, and the printed circuit board is configured to bepositioned within the channel opening and between the cable and theouter jacket.
 2. The cable assembly of claim 1, further comprising aninner jacket, wherein the inner jacket surrounds the cable and the outerjacket surrounds the inner jacket.
 3. The cable assembly of claim 1,wherein a first thickness between an outer layer and an inner layer ofthe outer jacket in a section of the outer jacket that includes thechannel opening is less than a second thickness between the outer layerand the inner layer of the outer jacket in another section of the outerjacket that does not include the channel opening.
 4. The cable assemblyof claim 1, wherein a shape of the channel opening is rectangular,square, circular, or trapezoidal.
 5. The cable assembly of claim 1,wherein the outer jacket includes a plurality of channel openings andwherein a plurality of printed circuit boards are configured to bepositioned within the plurality of channel openings between the cableand the outer jacket.
 6. The cable assembly of claim 1, wherein a depthof the channel opening is consistent throughout a length of the outerjacket.
 7. The cable assembly of claim 1, wherein a depth of the channelopening varies along a length of the outer jacket.
 8. The cable assemblyof claim 6, wherein the depth of the channel opening corresponds to adifference between a first thickness and a second thickness between anouter layer and an inner layer of the outer jacket, the first thicknessis measured between the outer layer and the inner layer of the outerjacket in a section of the outer jacket that includes the channelopening, and the second thickness is measured between the outer layerand the inner layer of the outer jacket in another section of the outerjacket that does not include the channel opening.
 9. The cable assemblyof claim 2, wherein the printed circuit board is configured to bepositioned within the channel opening between the inner jacket and theouter jacket.
 10. The cable assembly of claim 7, wherein the depth ofthe channel opening varies along the length of the outer jacket based ona size of the light emitting diodes.
 11. The cable assembly of claim 1,wherein the outer jacket is translucent.
 12. A cable assemblycomprising: an inner jacket; an outer jacket; a printed circuit boardincluding light emitting diodes; and a cable configured to transmitinformation, wherein the inner jacket includes a channel opening, andthe printed circuit board is configured to be positioned within thechannel opening and between the inner jacket and the outer jacket. 13.The cable assembly of claim 12, wherein the inner jacket surrounds thecable and the outer jacket surrounds the inner jacket.
 14. The cableassembly of claim 12, wherein a first thickness between an outer layerand an inner layer of the inner jacket in a section of the inner jacketthat includes the channel opening is less than a second thicknessbetween the outer layer and the inner layer of the inner jacket inanother section of the inner jacket that does not include the channelopening.
 15. The cable assembly of claim 12, wherein the inner jacketincludes a plurality of channel openings and wherein a plurality ofprinted circuit boards are configured to be positioned within theplurality of channel openings between the inner jacket and the outerjacket.
 16. The cable assembly of claim 12, wherein a depth of thechannel opening is consistent throughout a length of the outer jacket.17. The cable assembly of claim 16, wherein the depth of the channelopening corresponds to a difference between a first thickness and asecond thickness between an outer layer and an inner layer of the innerjacket, the first thickness is measured between the outer layer and theinner layer of the inner jacket in a section of the inner jacket thatincludes the channel opening, and the second thickness is measuredbetween the outer layer and the inner layer of the inner jacket inanother section of the inner jacket that does not include the channelopening.
 18. The cable assembly of claim 12, wherein the outer jacket istranslucent.
 19. An outer jacket for a cable that transmits information,the outer jacket comprising: an outer layer; and an inner layer, whereinthe inner layer comprises a channel opening to allow a plurality oflight emitting diodes to be housed within the channel opening.
 20. Aninner jacket for a cable that transmits information, the inner jacketcomprising: an inner layer; and an outer layer, wherein the outer layercomprises a channel opening to allow a plurality of light emittingdiodes to be housed within the channel opening.